Triple
T33254790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bob Dole presidential campaign |
E851345
|
entity |
| Predicate | candidatePreviousRole |
P18982
|
FINISHED |
| Object | Senate Majority Leader |
—
|
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: Senate Majority Leader | Statement: [Bob Dole presidential campaign, candidatePreviousRole, Senate Majority Leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: candidatePreviousRole Context triple: [Bob Dole presidential campaign, candidatePreviousRole, Senate Majority Leader]
-
A.
mayHavePriorRole
Indicates that an entity is allowed or expected to have held a specified role at some earlier time.
-
B.
economicRolePast
Indicates that an entity previously held a specific economic function, position, or role in the past.
-
C.
officePreviouslyHeldBy
chosen
Indicates that a particular office or position was formerly occupied by a specified person or entity.
-
D.
namedAfterOccupationOrRole
Indicates that an entity is named after a specific occupation, profession, or social role associated with a person or group.
-
E.
earlierOccupation
Indicates that one occupation held by an entity occurred before another occupation in that entity’s work history.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db34cc38819091fb536cf5b2e55c |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82fef788190b9ad19a36c0312dc |
completed | May 3, 2026, 5:08 a.m. |
Created at: May 1, 2026, 1:31 a.m.