Triple
T32496177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kangtega |
E830528
|
entity |
| Predicate | typicalApproachRoute |
P6174
|
FINISHED |
| Object | via Namche Bazaar and Khumjung |
—
|
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: via Namche Bazaar and Khumjung | Statement: [Kangtega, typicalApproachRoute, via Namche Bazaar and Khumjung]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalApproachRoute Context triple: [Kangtega, typicalApproachRoute, via Namche Bazaar and Khumjung]
-
A.
approachRoute
chosen
Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
-
B.
onStandardRouteOf
Indicates that something lies along or follows the usual, predefined, or officially designated route of another entity.
-
C.
standardRouteStartsFrom
Indicates that a standard or predefined route has its starting point at a specified location or entity.
-
D.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
E.
typicalEntryRoute
Indicates the usual or most common path or method by which something is entered or accessed.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:59 a.m.