Triple
T35688918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kachin conflict |
E1031233
|
entity |
| Predicate | ceasefireEndTime |
P184072
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Kachin conflict, ceasefireEndTime, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasefireEndTime Context triple: [Kachin conflict, ceasefireEndTime, 2011]
-
A.
ceasefireDuration
Indicates the length of time for which a ceasefire agreement between parties is intended to remain in effect.
-
B.
ceasefireDate
Indicates the date on which a ceasefire between parties is formally initiated, agreed, or comes into effect.
-
C.
ceasefireEnded
Indicates that a previously established ceasefire between parties has come to an end and hostilities may resume.
-
D.
ceasefireDeclared
Indicates that a formal agreement has been made to stop hostilities or armed conflict between opposing parties.
-
E.
ceasefireWith
Indicates a mutual agreement between parties to stop hostilities or armed conflict, typically for a specified period or under certain conditions.
- F. None of above. chosen
Provenance (4 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:05 p.m.