Triple
T23578531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korea |
E582133
|
entity |
| Predicate | armisticeSignedYear |
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: [Korea, armisticeSignedYear, 1953]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armisticeSignedYear Context triple: [Korea, armisticeSignedYear, 1953]
-
A.
armisticeSignedAt
Indicates the specific place where an armistice agreement was formally signed.
-
B.
armisticeSignedWith
Indicates that a formal agreement to stop fighting (an armistice) has been concluded between the two related parties.
-
C.
dateOfArmistice
Indicates the specific calendar date on which an armistice agreement between parties took effect.
-
D.
statusOfArmistice
Indicates the current condition or standing of an armistice agreement between parties.
-
E.
signedArmistice
Indicates that an entity formally agreed to and endorsed an armistice, marking the suspension of active hostilities between conflicting parties.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1afd7dbe88190b05ff03f952bf7c3 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:39 p.m.