Triple
T24261631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surkhob |
E604718
|
entity |
| Predicate | flowsThroughMountainRange |
P6786
|
FINISHED |
| Object | Pamir-Alay |
—
|
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: Pamir-Alay | Statement: [Surkhob, flowsThroughMountainRange, Pamir-Alay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsThroughMountainRange Context triple: [Surkhob, flowsThroughMountainRange, Pamir-Alay]
-
A.
crossesMountainRange
chosen
Indicates that one entity traverses from one side of a mountain range to the other, passing through or over it.
-
B.
crossesMountainRangeTo
Indicates that one entity traverses from one side of a mountain range to the other, passing across or through it as a route or connection.
-
C.
mountainRange
Indicates that one entity is a mountain range that the other entity is part of, associated with, or located in.
-
D.
mountainRangeType
Indicates the classification or category of a mountain range based on its geological or geographical type.
-
E.
sourceMountainRange
Indicates that a river, stream, or similar feature originates from or has its source in a specified mountain range.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c6727388190862e3ce09c372c70 |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:06 a.m.