Triple
T28291525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Afghan presidential election |
E713439
|
entity |
| Predicate | secondRoundHeld |
P52767
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [2019 Afghan presidential election, secondRoundHeld, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondRoundHeld Context triple: [2019 Afghan presidential election, secondRoundHeld, no]
-
A.
secondRoundDate
Indicates the date on which the second round of an event, process, or sequence is scheduled or occurs.
-
B.
includesSecondRound
chosen
Indicates that the referenced process, event, or activity contains or involves a second round or phase as part of its structure.
-
C.
secondRoundEndDate
Indicates the date on which the second round of an event, process, or activity concludes.
-
D.
secondRoundFormat
Indicates the structure or rules used to organize and conduct the second round of a multi-round process or competition.
-
E.
secondRoundCandidate
Indicates that an entity has advanced past an initial selection stage and is being considered as a candidate in a second round of evaluation or decision-making.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 27, 2026, 11:29 p.m.