Triple
T16465830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberalia |
E399929
|
entity |
| Predicate | comingOfAgeMarker |
P86266
|
FINISHED |
| Object | transition from boyhood to manhood |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: transition from boyhood to manhood | Statement: [Liberalia, comingOfAgeMarker, transition from boyhood to manhood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comingOfAgeMarker Context triple: [Liberalia, comingOfAgeMarker, transition from boyhood to manhood]
-
A.
cameOfAge
Indicates that an entity reached the age or stage of maturity at which it is considered an adult or fully responsible.
-
B.
transitionAge
Indicates a change in state or status of an entity from one defined phase, condition, or category to another at a particular point or period in time.
-
C.
typicallyIssuedAtAge
Indicates the age at which something is most commonly or customarily issued to an individual.
-
D.
hasGenderMilestone
chosen
Indicates that an entity has reached or is associated with a significant event or transition related to its gender.
-
E.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dcc52f88190958b408e49cfb512 |
completed | April 18, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:11 a.m.