Triple
T18600322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macon Dead III |
E454601
|
entity |
| Predicate | numericalOrderInFamily |
P125150
|
FINISHED |
| Object | III |
—
|
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: III | Statement: [Macon Dead III, numericalOrderInFamily, III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numericalOrderInFamily Context triple: [Macon Dead III, numericalOrderInFamily, III]
-
A.
positionInFamilyBirthOrder
Indicates the relative order in which a person was born within their family (e.g., first-born, middle child, last-born).
-
B.
ordinalNumber
Indicates the position or rank of an entity within an ordered sequence (e.g., first, second, third).
-
C.
ordinalInFamilyTitle
Indicates that a title or role specifies an entity’s numerical position within a family sequence (e.g., first, second, third).
-
D.
hasOrdinalInFamilyLine
chosen
Indicates that an entity holds a specific ordinal position (e.g., first, second, third) within a family lineage or sequence of family members.
-
E.
positionInFamilyTree
Indicates the familial relationship or generational position one person holds relative to another within a family tree.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5475018548190a2f497081af7ce55 |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.