Triple
T4162926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Chechen War |
E91571
|
entity |
| Predicate | officialEndDate |
P49551
|
FINISHED |
| Object | 2009-04-16 |
—
|
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-04-16 | Statement: [Second Chechen War, officialEndDate, 2009-04-16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialEndDate Context triple: [Second Chechen War, officialEndDate, 2009-04-16]
-
A.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
B.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
C.
endDateOfficialUse
chosen
Indicates the date on which the official use or validity of something (such as a document, status, or authorization) comes to an end.
-
D.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
E.
finalSectionOpeningDate
Indicates the date on which the last or concluding section of something is officially opened or becomes available.
- 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_69aed9626ebc8190a39de631788bea3e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.