Triple
T12548853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Korea |
E300041
|
entity |
| Predicate | preWarContinuityWith |
P105845
|
FINISHED |
| Object | territory of South Korea |
—
|
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: territory of South Korea | Statement: [Southern Korea, preWarContinuityWith, territory of South Korea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preWarContinuityWith Context triple: [Southern Korea, preWarContinuityWith, territory of South Korea]
-
A.
prewarStatus
Indicates the condition, role, or circumstances of an entity as they existed before a specific war or armed conflict.
-
B.
preWarCharacter
Indicates that a character existed or had a particular state or role prior to a specified war or conflict.
-
C.
preWarCountry
Indicates that a country existed or held a particular status prior to a specified war or major armed conflict.
-
D.
preWarServiceArea
Indicates the geographic area or jurisdiction in which an entity operated or provided service before a specified war or conflict.
-
E.
precededDeclarationOfWar
Indicates that one event or action occurred before and led up to a formal declaration of war.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d95f5148948190946a575d812b329d |
completed | April 10, 2026, 8:36 p.m. |
Created at: April 8, 2026, 9:58 p.m.