Triple
T23404928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaepung County |
E559608
|
entity |
| Predicate | reassignmentCountry |
P152131
|
FINISHED |
| Object | North Korea |
—
|
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: North Korea | Statement: [Kaepung County, reassignmentCountry, North Korea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reassignmentCountry Context triple: [Kaepung County, reassignmentCountry, North Korea]
-
A.
reassignedHostCountry
Indicates that an entity’s associated host country has been changed from a previous one to a new one.
-
B.
changedCountryAfter
Indicates that an entity moved from one country to another at some point after a specified reference time or event.
-
C.
notReassignedToAnotherCountry
Indicates that an entity has not been transferred or assigned from its current country to a different country.
-
D.
reassignedHostContinent
Indicates that the host entity has been moved or transferred from its original continent to a different continent.
-
E.
renamingCountry
Indicates that one country is changing its official name to a new one.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4e27db88190b37375b38073291c |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:38 p.m.