Triple
T23579107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korea |
E582149
|
entity |
| Predicate | divisionFormalizedBy |
P50238
|
FINISHED |
| Object | Korean Armistice Agreement |
—
|
NE NERFINISHED |
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: Korean Armistice Agreement | Statement: [Korea, divisionFormalizedBy, Korean Armistice Agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionFormalizedBy Context triple: [Korea, divisionFormalizedBy, Korean Armistice Agreement]
-
A.
divisionRenamedFrom
Indicates that a division currently known by one name was previously known by another specified name.
-
B.
divisionContext
Indicates the situational or conceptual setting in which a division operation or separation between entities takes place.
-
C.
formalizedDivisionOf
chosen
Indicates a relationship where one entity is officially and explicitly divided into distinct parts or sub-entities according to a formal rule, structure, or agreement.
-
D.
divisionRenamedTo
Indicates that an organizational division has changed its name to a new specified name.
-
E.
divisionSince
Indicates that one entity has been divided or split from another starting at a specific point in time.
- 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_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. |
Created at: April 17, 2026, 6:39 p.m.