Triple
T2495047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malakand Division |
E52134
|
entity |
| Predicate | strategicRoute |
P24772
|
FINISHED |
| Object | access to Chitral |
—
|
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: access to Chitral | Statement: [Malakand Division, strategicRoute, access to Chitral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicRoute Context triple: [Malakand Division, strategicRoute, access to Chitral]
-
A.
routeOptimization
Indicates the process of determining the most efficient path or sequence of paths between locations according to specified criteria such as distance, time, or cost.
-
B.
routeBetween
chosen
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
C.
strategicLocation
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
-
D.
streetPlanBy
Indicates that a street or road layout was designed, organized, or planned by a particular agent or authority.
-
E.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd19541048190b9e39db119c20fe8 |
completed | March 7, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69abd0b980b481908d4932bcea4a6167 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.