Triple
T28291524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Afghan presidential election |
E713439
|
entity |
| Predicate | firstRoundHeld |
P47097
|
FINISHED |
| Object | 2019-09-28 |
—
|
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: 2019-09-28 | Statement: [2019 Afghan presidential election, firstRoundHeld, 2019-09-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRoundHeld Context triple: [2019 Afghan presidential election, firstRoundHeld, 2019-09-28]
-
A.
firstRound
Indicates that the referenced event, match, or interaction occurs in the initial or opening round of a multi-round process or competition.
-
B.
firstRoundDate
chosen
Indicates the date on which the first round of an event, process, or competition takes place.
-
C.
firstRoundRequired
Indicates that an initial or preliminary round must take place before subsequent stages or actions can proceed.
-
D.
firstRoundEndDate
Indicates the date on which the first round of an event, process, or competition concludes.
-
E.
firstRoundResult
Indicates the outcome or status achieved by an entity in the first round of a multi-round process, competition, or evaluation.
- 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_69fff328ddc0819080642334a41fcf95 |
completed | May 10, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69fff2e0971c819081aa66f4a6a34b28 |
completed | May 10, 2026, 2:52 a.m. |
Created at: April 27, 2026, 11:29 p.m.