Triple
T15984033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kachin Independence Organization |
E387645
|
entity |
| Predicate | ceasefireYear |
P23514
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Kachin Independence Organization, ceasefireYear, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasefireYear Context triple: [Kachin Independence Organization, ceasefireYear, 1994]
-
A.
ceasefireDate
chosen
Indicates the date on which a ceasefire between parties is formally initiated, agreed, or comes into effect.
-
B.
ceasefireEnded
Indicates that a previously established ceasefire between parties has come to an end and hostilities may resume.
-
C.
ceasefireDeclared
Indicates that a formal agreement has been made to stop hostilities or armed conflict between opposing parties.
-
D.
ceasefireResolution
Indicates a formal decision or agreement to halt hostilities or armed conflict between opposing parties, typically under specified terms and conditions.
-
E.
conflictEndYear
Indicates the calendar year in which a particular conflict, dispute, or war came to an end.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.