Triple
T22849206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asia/Ulaanbaatar |
E566310
|
entity |
| Predicate | linkedToCountryCapital |
P76415
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Asia/Ulaanbaatar, linkedToCountryCapital, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToCountryCapital Context triple: [Asia/Ulaanbaatar, linkedToCountryCapital, yes]
-
A.
hasCountryCapitalConnection
Indicates a relationship in which a specific country is associated with its official capital city.
-
B.
countryCapitalConnection
chosen
Indicates a relationship where a specific city serves as the official capital of a particular country.
-
C.
connectsCountryCapitalToCity
Indicates a relationship that links a country’s capital to a specific city associated with that country.
-
D.
governingCountryCapitalConnectedTo
Indicates that the capital city of the governing country is directly connected (e.g., via infrastructure, transport, or communication links) to the referenced location or entity.
-
E.
associatedCountryCapital
Indicates that a country is related to, or paired with, its capital city.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e8aceb88190b137d17a7510fee4 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:36 p.m.