Triple
T17124399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamir Face |
E415553
|
entity |
| Predicate | isRouteTo |
P50556
|
FINISHED |
| Object | summit of Nanga Parbat |
—
|
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: summit of Nanga Parbat | Statement: [Diamir Face, isRouteTo, summit of Nanga Parbat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRouteTo Context triple: [Diamir Face, isRouteTo, summit of Nanga Parbat]
-
A.
isRouteFor
chosen
Indicates that one entity serves as a path, course, or channel used for traveling, transporting, or connecting to another entity.
-
B.
isPartOfRoute
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
C.
isStandardRouteOn
Indicates that a particular route is the default or officially designated path used on a given transportation line or service.
-
D.
mayRouteTo
Indicates that one entity is permitted or able to direct, forward, or transfer something (such as data, traffic, or requests) to another entity.
-
E.
isAccessRouteAround
Indicates that one entity serves as an access route that goes around or circumvents another entity.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f025fce481908e261f2e363e14f9 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e35d6d20808190a38bb32e2294bc48 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:36 a.m.