Triple
T19051952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thai–Japanese armistice |
E466281
|
entity |
| Predicate | typeOfConflictSettlement |
P50821
|
FINISHED |
| Object | ceasefire agreement |
—
|
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: ceasefire agreement | Statement: [Thai–Japanese armistice, typeOfConflictSettlement, ceasefire agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfConflictSettlement Context triple: [Thai–Japanese armistice, typeOfConflictSettlement, ceasefire agreement]
-
A.
conflictType
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
B.
settingOfConflict
Indicates the location or context in which a conflict between entities takes place.
-
C.
conflictResolvedBy
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified entity or process.
-
D.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
-
E.
typeOfCeasefire
chosen
Indicates the specific category or nature of a ceasefire agreement that applies between parties in a conflict.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc031ff881908e8c68c7aaff3733 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.