Triple
T33058486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Bush |
E845907
|
entity |
| Predicate | hasPaternalGreatUncle |
P190024
|
FINISHED |
| Object | George W. Bush |
—
|
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: George W. Bush | Statement: [John Bush, hasPaternalGreatUncle, George W. Bush]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPaternalGreatUncle Context triple: [John Bush, hasPaternalGreatUncle, George W. Bush]
-
A.
hasPaternalGrandparent
Indicates that one entity is the paternal grandparent (father’s parent) of another entity.
-
B.
paternalGreatGranduncle
chosen
Indicates that one person is the brother of another person's paternal great-grandparent (father's grandparent).
-
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.
paternalGreatGrandparentOf
Indicates that one person is the father of another person’s grandparent, making him that person’s paternal great-grandparent.
-
E.
paternalNephewOf
Indicates that one person is the son of another person's brother (i.e., the nephew related through the father's side).
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: May 1, 2026, 1:25 a.m.