Triple
T6474719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Congress of Bolivia |
E146040
|
entity |
| Predicate | supersessionYear |
P34991
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [National Congress of Bolivia, supersessionYear, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supersessionYear Context triple: [National Congress of Bolivia, supersessionYear, 2009]
-
A.
successionYear
chosen
Indicates the calendar year in which one entity formally succeeded or took over from another in a given role, position, or status.
-
B.
suppressionYear
Indicates the year in which the referenced activity, expression, or entity was formally suppressed, halted, or forcibly discontinued.
-
C.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
D.
supersededInCentury
Indicates that one entity has been replaced or rendered obsolete by another during a specified century.
-
E.
successorAdoptionYear
Indicates the year in which a successor entity formally adopted or took over from its predecessor.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a341360819082f2b5496a1a68b0 |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:50 p.m.