Triple
T18132065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Bonior |
E434036
|
entity |
| Predicate | heldLeadershipRole |
P115779
|
FINISHED |
| Object | Chief Deputy Whip |
—
|
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: Chief Deputy Whip | Statement: [David Bonior, heldLeadershipRole, Chief Deputy Whip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldLeadershipRole Context triple: [David Bonior, heldLeadershipRole, Chief Deputy Whip]
-
A.
heldPoliticalOfficeIn
Indicates that an entity served in a political office or position within a specified governmental body or jurisdiction.
-
B.
heldJudicialPositionIn
Indicates that an entity served in an official judicial role or office within a specified jurisdiction or court.
-
C.
hadLeadershipFrom
Indicates that one entity received leadership, guidance, or direction from another entity.
-
D.
hasLeaderHeldOffice
Indicates that the specified leader has occupied or served in an official office or position.
-
E.
leadershipRoleAtRepresentativeLevel
chosen
Indicates that an entity holds a leadership position at a representative or delegate level within an organization or governing body.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddf2c68881909dfbe59df15ddccc |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.