Triple
T11733168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muztagh Ata |
E278951
|
entity |
| Predicate | standardRouteFeatures |
P10970
|
FINISHED |
| Object | long glacier slopes |
—
|
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: long glacier slopes | Statement: [Muztagh Ata, standardRouteFeatures, long glacier slopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardRouteFeatures Context triple: [Muztagh Ata, standardRouteFeatures, long glacier slopes]
-
A.
notableRouteFeature
chosen
Indicates that a route is associated with a distinctive or significant feature, such as a landmark, characteristic terrain, or other notable aspect along its path.
-
B.
notableRouteType
Indicates that a route is particularly significant or well-known for a specific type or category (e.g., scenic, historic, commercial).
-
C.
usedRoutes
Indicates that an entity has utilized or traveled along specific routes.
-
D.
signpostFeature
Indicates that one entity serves as a signpost-related feature or element associated with another entity.
-
E.
routeDescription
Indicates a textual explanation or summary of the path, course, or itinerary taken between locations.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4daa7f48190896fc7653e9dd70b |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.