Triple
T34626088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kunlun–Pamir border region |
E889140
|
entity |
| Predicate | mountainRangeConvergenceOf |
P179712
|
FINISHED |
| Object | Kunlun Mountains |
E123638
|
NE 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: Kunlun Mountains | Statement: [Kunlun–Pamir border region, mountainRangeConvergenceOf, Kunlun Mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainRangeConvergenceOf Context triple: [Kunlun–Pamir border region, mountainRangeConvergenceOf, Kunlun Mountains]
-
A.
mountainRange
Indicates that one entity is a mountain range that the other entity is part of, associated with, or located in.
-
B.
mountainRangeType
Indicates the classification or category of a mountain range based on its geological or geographical type.
-
C.
sourceMountainRange
Indicates that a river, stream, or similar feature originates from or has its source in a specified mountain range.
-
D.
shareMountainRange
Indicates that two geographic entities are located within or along the same mountain range.
-
E.
mountainRangeFormed
Indicates that a specific mountain range came into existence or was created, typically through geological processes.
- F. None of above. chosen
Provenance (5 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3748e8ef008190aae7c90739d49e3b |
completed | June 21, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 2:04 a.m.