Triple
T27022870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KNU |
E680710
|
entity |
| Predicate | signedNationwideCeasefireAgreement |
P102140
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [KNU, signedNationwideCeasefireAgreement, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedNationwideCeasefireAgreement Context triple: [KNU, signedNationwideCeasefireAgreement, 2015]
-
A.
ceasefireSignedBy
chosen
Indicates that a formal ceasefire agreement has been signed by the specified party or parties.
-
B.
ceasefireAgreements
Indicates that parties involved in a conflict have formally agreed to suspend hostilities, typically under specified terms and conditions.
-
C.
ceasefireDeclared
Indicates that a formal agreement has been made to stop hostilities or armed conflict between opposing parties.
-
D.
ceasefireWith
Indicates a mutual agreement between parties to stop hostilities or armed conflict, typically for a specified period or under certain conditions.
-
E.
announcedCeasefire
Indicates that an entity has formally declared the suspension of hostilities or fighting, typically within a conflict or war.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:09 a.m.