Triple
T28851388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tilicho Lake |
E728603
|
entity |
| Predicate | nearestMajorTrekkingHub |
P171802
|
FINISHED |
| Object | Manang |
—
|
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: Manang | Statement: [Tilicho Lake, nearestMajorTrekkingHub, Manang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestMajorTrekkingHub Context triple: [Tilicho Lake, nearestMajorTrekkingHub, Manang]
-
A.
nearestMajorTrailPass
Indicates the relationship where a given location is associated with the closest significant trail crossing or pass along a major trail network.
-
B.
nearbyHillStation
Indicates that one location is a hill station situated close to another specified place.
-
C.
nearbySummit
Indicates that one summit is located close to another summit in geographic space.
-
D.
commonAcclimatizationHikeDestinationFrom
Indicates that a location is a typical or frequently used hiking destination for acclimatization starting from a given origin.
-
E.
hikingTrailPassesNear
Indicates that a hiking trail runs close to, but does not directly intersect or pass through, a specified location or feature.
- F. None of above. chosen
Provenance (4 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 28, 2026, 6:44 a.m.