Triple
T27609153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Machha Khola |
E700266
|
entity |
| Predicate | typicalUseOnTrek |
P201193
|
FINISHED |
| Object | first or second overnight stop from trailhead |
—
|
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: first or second overnight stop from trailhead | Statement: [Machha Khola, typicalUseOnTrek, first or second overnight stop from trailhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUseOnTrek Context triple: [Machha Khola, typicalUseOnTrek, first or second overnight stop from trailhead]
-
A.
hikingUse
Indicates the use or engagement in hiking as an activity or means of travel.
-
B.
trekkingFeature
Indicates a notable characteristic, condition, or element specifically associated with trekking activities or routes.
-
C.
trekkingBase
Indicates a location that serves as the primary starting point or support hub for trekking activities.
-
D.
typicalUseOnAscent
Indicates that something is commonly or normally used during the ascent phase of an activity, process, or journey.
-
E.
trekType
Indicates the specific category or style of trekking activity associated with an entity.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ffde9263248190996f970b6cf6e49d |
completed | May 10, 2026, 1:25 a.m. |
| PD | Predicate disambiguation | batch_69ffdd760f1c8190abc6c0c1cd97ba5f |
completed | May 10, 2026, 1:20 a.m. |
| PDg | Predicate description generation | batch_69ffde916fcc81908d6e1b4e6d3f761c |
completed | May 10, 2026, 1:25 a.m. |
Created at: April 27, 2026, 2:10 p.m.