Triple

T11225020
Position Surface form Disambiguated ID Type / Status
Subject Dir E265671 entity
Predicate hasRoadImportance P19386 FINISHED
Object key route to Chitral via Lowari Pass 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: key route to Chitral via Lowari Pass | Statement: [Dir, hasRoadImportance, key route to Chitral via Lowari Pass]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRoadImportance
Context triple: [Dir, hasRoadImportance, key route to Chitral via Lowari Pass]
  • A. roadImportance chosen
    Indicates the relative significance or priority of a road within a transportation network, such as its role in connectivity, traffic flow, or access.
  • B. routeImportance
    Indicates the relative significance or priority of a route compared to other possible routes, typically in terms of usefulness, relevance, or preference.
  • C. isMajorRoadIn
    Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
  • D. isMainRoad
    Indicates that a road serves as a primary or major thoroughfare within a transportation network.
  • E. hasMajorTransportationRole
    Indicates that an entity plays a primary or significant role in providing or supporting transportation services or infrastructure.
  • 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_69d6aac656d48190b275efaa7d6074ee completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8ee15d4819087449058addef597 completed April 9, 2026, 5:59 p.m.
PD Predicate disambiguation batch_69d75cfbbb188190861efd5d94fe27da completed April 9, 2026, 8:02 a.m.
Created at: April 8, 2026, 9:30 p.m.