Triple
T20498107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaesong |
E503225
|
entity |
| Predicate | capitalOfEnd |
P135987
|
FINISHED |
| Object | 1392 |
—
|
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: 1392 | Statement: [Kaesong, capitalOfEnd, 1392]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfEnd Context triple: [Kaesong, capitalOfEnd, 1392]
-
A.
capitalUnder
Indicates that one entity serves as the capital city or administrative center subordinate to, or governed by, another entity.
-
B.
finalCity
Indicates that a given city is the last or ultimate city associated with an entity within a sequence, process, or journey.
-
C.
capitalOftenLocatedIn
Indicates that the capital city of a region or country is frequently, though not always, situated within a particular location or type of area.
-
D.
lostCapital
Indicates that an entity has ceased to be the capital of a political or administrative region.
-
E.
endPointIsCapitalOf
chosen
Indicates that the endpoint entity serves as the capital city of the other related entity (typically a country, state, or region).
- 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cbefe4c819098af5bfd4d92341d |
completed | April 20, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:35 a.m.