Triple
T8393849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julia Antonia |
E198005
|
entity |
| Predicate | paternalUncleHeldOffice |
P81980
|
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: [Julia Antonia, paternalUncleHeldOffice, consul of the Roman Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paternalUncleHeldOffice Context triple: [Julia Antonia, paternalUncleHeldOffice, consul of the Roman Republic]
-
A.
uncleOrAuntOf
Indicates that one person is the uncle or aunt of another person, typically as the sibling (or sibling-in-law) of the other person’s parent.
-
B.
granduncleOf
Indicates that one person is the brother of another person's grandparent.
-
C.
halfUncleOf
Indicates a familial relationship where one person is the half-brother of a parent of another person, making him that person's half-uncle.
-
D.
hasPaternalGrandparent
Indicates that one entity is the paternal grandparent (father’s parent) of another entity.
-
E.
uncle
Indicates a familial relationship where one person is the brother (or brother-in-law) of another person's parent.
- F. None of above. chosen
Provenance (4 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8185ef60819085cfa7491d35834a |
completed | March 31, 2026, 8:10 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:03 p.m.