Triple
T16351926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khasavyurt Accord |
E397079
|
entity |
| Predicate | postponedIssueUntil |
P18028
|
FINISHED |
| Object | not earlier than 2001 |
—
|
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: not earlier than 2001 | Statement: [Khasavyurt Accord, postponedIssueUntil, not earlier than 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postponedIssueUntil Context triple: [Khasavyurt Accord, postponedIssueUntil, not earlier than 2001]
-
A.
postponedFrom
Indicates that an event or action has been rescheduled to occur at a later time than originally planned.
-
B.
postponedToYear
chosen
Indicates that an event or action has been delayed and rescheduled to occur in the specified calendar year.
-
C.
definedIssueAsDeferred
Indicates that an issue has been explicitly marked or classified as deferred, meaning its resolution or handling is postponed to a later time.
-
D.
postponementReason
Indicates the reason or cause for which an event, action, or decision has been delayed or rescheduled.
-
E.
rescheduledTo
Indicates that an event or action has been moved from its original time to a new specified time.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2facbf60c8190aa47d4c45ff59354 |
completed | April 18, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.