Triple
T23721841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China and North Korea |
E586165
|
entity |
| Predicate | KoreanWarArmisticeYear |
P153250
|
FINISHED |
| Object | 1953 |
—
|
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: 1953 | Statement: [China and North Korea, KoreanWarArmisticeYear, 1953]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: KoreanWarArmisticeYear Context triple: [China and North Korea, KoreanWarArmisticeYear, 1953]
-
A.
status1949Armistice
Indicates that a relationship or situation is governed by the terms and conditions of the 1949 Armistice agreements.
-
B.
armisticeSignedYear
chosen
Indicates the year in which an armistice agreement was formally signed between the involved parties.
-
C.
conflictEndYear
Indicates the calendar year in which a particular conflict, dispute, or war came to an end.
-
D.
dateOfArmistice
Indicates the specific calendar date on which an armistice agreement between parties took effect.
-
E.
armisticeSignedAt
Indicates the specific place where an armistice agreement was formally signed.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b91177c08190bea6e62ed13e2495 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:02 p.m.