Triple
T23651968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keijō |
E584189
|
entity |
| Predicate | afterEndOfColonialRule |
P64803
|
FINISHED |
| Object | name reverted to Seoul |
—
|
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: name reverted to Seoul | Statement: [Keijō, afterEndOfColonialRule, name reverted to Seoul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterEndOfColonialRule Context triple: [Keijō, afterEndOfColonialRule, name reverted to Seoul]
-
A.
colonialLegacy
Indicates the enduring influence or consequences of a past colonial relationship that continue to shape interactions or conditions between entities.
-
B.
periodOfColonialRule
Indicates the time span during which one political power exercised colonial control over another territory or people.
-
C.
decolonizationOutcome
Indicates the result or consequences that follow from a process of decolonization.
-
D.
usedAfterIndependenceOf
chosen
Indicates that one entity came into use only after the other entity achieved independence.
-
E.
preColonialStatus
Indicates the condition, role, or social-political standing an entity held prior to the onset of colonial rule.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b358ce448190a654d2cd3e81ef83 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.