Triple
T26039130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O'Neill |
E647636
|
entity |
| Predicate | isBorneByNotablePeopleIn |
P160320
|
FINISHED |
| Object | politics |
—
|
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: politics | Statement: [O'Neill, isBorneByNotablePeopleIn, politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBorneByNotablePeopleIn Context triple: [O'Neill, isBorneByNotablePeopleIn, politics]
-
A.
hasNotablePersonBornHere
Indicates that a notable or distinguished person was born at the referenced place.
-
B.
hasProminentPlaceOn
Indicates that one entity occupies a highly visible, important, or emphasized position on another entity (such as a surface, list, or layout).
-
C.
notableAsNamesakeOf
Indicates that one entity is recognized or distinguished specifically for being the namesake of another entity.
-
D.
namedPersonNotableFor
Indicates that a person is especially known or recognized for a particular work, role, achievement, or characteristic.
-
E.
hasNotablePeople
Indicates that certain people associated with an entity are distinguished or noteworthy in some recognized way.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60620fb648190826cfb2fdefe4858 |
completed | May 2, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 22, 2026, 9:08 a.m.