Triple
T23406000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khandagaity–Borshoo |
E559934
|
entity |
| Predicate | connectsRegionInMongolia |
P112692
|
FINISHED |
| Object | Uvs Province |
—
|
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: Uvs Province | Statement: [Khandagaity–Borshoo, connectsRegionInMongolia, Uvs Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsRegionInMongolia Context triple: [Khandagaity–Borshoo, connectsRegionInMongolia, Uvs Province]
-
A.
hasNeighboringMongolianRegion
Indicates that one region is geographically adjacent to, and shares a border with, a region located in Mongolia.
-
B.
borderMongolianAimags
Indicates that two Mongolian aimags (provinces) share a common land border.
-
C.
connectsRegions
Indicates a relationship where one entity links or joins two or more distinct regions, enabling passage, interaction, or continuity between them.
-
D.
connectsProvinceOrRegion
chosen
Indicates that one entity serves to link or provide a connection between a specific province or region and another entity.
-
E.
connectsProvincesAlong
Indicates a relationship where something serves as a link or route joining multiple provinces along a specified path or alignment.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4e364548190b98dc09240fba58e |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:38 p.m.