Triple
T29058307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attalus (father of Attalus I) |
E735453
|
entity |
| Predicate | paternalAncestorOf |
P87675
|
FINISHED |
| Object | Attalus I |
—
|
NE NERFINISHED |
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: Attalus I | Statement: [Attalus (father of Attalus I), paternalAncestorOf, Attalus I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paternalAncestorOf Context triple: [Attalus (father of Attalus I), paternalAncestorOf, Attalus I]
-
A.
paternalGrandchildOf
Indicates that one entity is the grandchild of another through the latter’s son (i.e., via the paternal line).
-
B.
paternalGreatGrandfatherOf
Indicates that one person is the father of another person's paternal grandfather.
-
C.
paternalUncleInstanceOf
Indicates that one entity is a specific instance of the paternal uncle relationship to another entity (i.e., the brother of the person's father).
-
D.
forefatherOf
chosen
Indicates that one person is an ancestor, typically from an earlier generation, of another person.
-
E.
hasPaternalGrandparent
Indicates that one entity is the paternal grandparent (father’s parent) of another entity.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6609457148190aa52f24617101f50 |
completed | May 2, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 10:13 a.m.