Triple
T11819495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 Russian presidential election |
E281086
|
entity |
| Predicate | wasSingleRound |
P101669
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [2000 Russian presidential election, wasSingleRound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSingleRound Context triple: [2000 Russian presidential election, wasSingleRound, true]
-
A.
reachedRound
Indicates that an entity has advanced to or attained a particular round or stage within a process, event, or competition.
-
B.
hasRound
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
-
C.
hasProperRounds
Indicates that an entity is associated with rounds that meet specified standards or criteria for being considered proper or valid.
-
D.
divisionalRoundIncluded
Indicates that the referenced entity includes or pertains to the divisional round stage within a larger competition or playoff structure.
-
E.
eliminatedInRound
Indicates that an entity was removed from further participation or competition during a specified round.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e87e488190905bc3bb6d721e56 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:42 p.m.