Triple
T27609213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dharapani |
E700268
|
entity |
| Predicate | locatedOnTrekRoute |
P158095
|
FINISHED |
| Object | Annapurna Circuit |
—
|
NE NERFINISHED |
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: Annapurna Circuit | Statement: [Dharapani, locatedOnTrekRoute, Annapurna Circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnTrekRoute Context triple: [Dharapani, locatedOnTrekRoute, Annapurna Circuit]
-
A.
locatedOnTrekkingRoute
chosen
Indicates that something is situated along or directly on a designated trekking or hiking route.
-
B.
locatedOnRouteTo
Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
-
C.
trailLocatedIn
Indicates that a trail is situated within or passes through a specified geographic area or region.
-
D.
locatedOnPeak
Indicates that one entity is situated at or on the summit or highest point of another entity (a peak).
-
E.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: April 27, 2026, 2:10 p.m.