Triple
T38506084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annapurna Sanctuary |
E921766
|
entity |
| Predicate | mainTrailEnd |
P126282
|
FINISHED |
| Object | Annapurna Base Camp |
—
|
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 Base Camp | Statement: [Annapurna Sanctuary, mainTrailEnd, Annapurna Base Camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainTrailEnd Context triple: [Annapurna Sanctuary, mainTrailEnd, Annapurna Base Camp]
-
A.
longDistanceTrailEnd
Indicates that a location serves as the endpoint or terminus of a long-distance trail.
-
B.
loopTrail
Indicates that a trail or path forms a closed loop, starting and ending at the same point without backtracking over the same segment.
-
C.
reachedFromTrailhead
Indicates that a location or point can be accessed by traveling from a designated trailhead.
-
D.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
E.
trailEndpoint
chosen
Indicates that one entity marks the terminal point or ending location of a trail defined by 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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 3, 2026, 4:32 p.m.