Triple
T6008335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidential sash of Bolivia |
E133768
|
entity |
| Predicate | predecessorHolder |
P6041
|
FINISHED |
| Object | outgoing President of Bolivia |
—
|
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: outgoing President of Bolivia | Statement: [Presidential sash of Bolivia, predecessorHolder, outgoing President of Bolivia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorHolder Context triple: [Presidential sash of Bolivia, predecessorHolder, outgoing President of Bolivia]
-
A.
predecessorTitleHolder
chosen
Indicates that one entity previously held a particular title or position before another entity.
-
B.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
C.
predecessorOperator
Indicates that one operator precedes another in an ordered sequence or process.
-
D.
predecessorLocatedAt
Indicates that the location specified was the place where the immediately preceding version, state, or instance of an entity was situated.
-
E.
predecessorBody
Indicates that one body or entity previously held a role, position, or status that is now occupied by another body or entity.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f154ca481909431baf4feecc16d |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.