Triple
T7838728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 Afghan presidential election |
E181749
|
entity |
| Predicate | plannedRunoffDate |
P61320
|
FINISHED |
| Object | 2009-11-07 |
—
|
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-11-07 | Statement: [2009 Afghan presidential election, plannedRunoffDate, 2009-11-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedRunoffDate Context triple: [2009 Afghan presidential election, plannedRunoffDate, 2009-11-07]
-
A.
runoffDate
chosen
Indicates the date on which a runoff event (such as a runoff election or runoff water occurrence) takes place or is scheduled.
-
B.
plannedAt
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
C.
datePlanned
Indicates that a specific date has been scheduled or intended for a particular event, action, or relationship to occur.
-
D.
rolloutDate
Indicates the date on which something (such as a product, feature, or policy) is first introduced or made available for general use.
-
E.
finalAppTransitionDate
Indicates the date on which the final transition or change of state for the application was completed.
- 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb14c336f08190a21a3fcaa7269457 |
completed | March 31, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:47 p.m.