Triple
T27246333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singalila Ridge |
E687353
|
entity |
| Predicate | popularTrekRoute |
P146014
|
FINISHED |
| Object | Sandakphu trek |
—
|
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: Sandakphu trek | Statement: [Singalila Ridge, popularTrekRoute, Sandakphu trek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularTrekRoute Context triple: [Singalila Ridge, popularTrekRoute, Sandakphu trek]
-
A.
popularRouteOn
Indicates that a particular route is frequently used or favored on a given transportation line, service, or network.
-
B.
popularRouteTo
chosen
Indicates that one location is widely used or frequently chosen as a route or way to reach another location.
-
C.
popularRouteFrom
Indicates a frequently chosen or well-traveled route that starts from a given origin location.
-
D.
popularRouteVia
Indicates that a route between two locations commonly or frequently passes through a specified intermediate point or path.
-
E.
travelRouteContext
Indicates the contextual details (such as purpose, conditions, or circumstances) under which a particular travel route is taken or defined.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 27, 2026, 10:41 a.m.