Triple
T28526189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danforth |
E721910
|
entity |
| Predicate | bearerOfficeHeld |
P172378
|
FINISHED |
| Object | United States Senator from Indiana |
—
|
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: United States Senator from Indiana | Statement: [Danforth, bearerOfficeHeld, United States Senator from Indiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerOfficeHeld Context triple: [Danforth, bearerOfficeHeld, United States Senator from Indiana]
-
A.
heldOf
Indicates that something is possessed, controlled, or kept by a particular entity.
-
B.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
-
C.
holdingOf
Indicates that one entity is in possession of, or physically grasping, another entity.
-
D.
holdingEffect
Indicates that one entity is maintaining possession or control of another entity, resulting in a particular effect or state during the period of holding.
-
E.
frontHeldBy
Indicates that the front side or leading part of an object is being physically supported or grasped by another entity.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 28, 2026, 3:24 a.m.