Triple
T20498106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaesong |
E503225
|
entity |
| Predicate | capitalOfStart |
P30707
|
FINISHED |
| Object | 918 |
—
|
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: 918 | Statement: [Kaesong, capitalOfStart, 918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfStart Context triple: [Kaesong, capitalOfStart, 918]
-
A.
capitalUnder
Indicates that one entity serves as the capital city or administrative center subordinate to, or governed by, another entity.
-
B.
hostsCapitalOf
Indicates that one location serves as the capital city of another administrative or political entity.
-
C.
capitalLocation
Indicates the relationship in which a place serves as the capital city or administrative center of a given political or geographic entity.
-
D.
startPointIsCapitalOf
Indicates that the starting point in a relation or path is a city that serves as the capital of the relevant region, country, or administrative entity.
-
E.
capitalOfFrom
chosen
Indicates that a city serves or served as the capital of a specified political entity during a particular time or from a particular source context.
- 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.