Triple
T8924762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mucia Tertia |
E212512
|
entity |
| Predicate | maternalGrandfatherOffice |
P51993
|
FINISHED |
| Object | consul of the Roman Republic |
—
|
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: consul of the Roman Republic | Statement: [Mucia Tertia, maternalGrandfatherOffice, consul of the Roman Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maternalGrandfatherOffice Context triple: [Mucia Tertia, maternalGrandfatherOffice, consul of the Roman Republic]
-
A.
maternalGrandfatherOf
chosen
Indicates that one person is the father of another person's mother.
-
B.
maternalGreatGrandfather
Indicates that one entity is the father of the mother of another entity’s mother (i.e., the person’s maternal great-grandfather).
-
C.
maternalGrandsonOf
Indicates that one entity is the male child of the daughter of another entity (i.e., the other entity’s grandson through their maternal line).
-
D.
spouseGrandfather
Indicates that one person is the grandfather of another person’s spouse.
-
E.
paternalUncleHeldOffice
Indicates that a person’s paternal uncle (their father’s brother) occupied or held a particular office or official position.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66547de881909ea9bfd104b32893 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.