Triple
T27743473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Passes trek |
E701915
|
entity |
| Predicate | typicalEndingPoint |
P18251
|
FINISHED |
| Object | Lukla |
—
|
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: Lukla | Statement: [Three Passes trek, typicalEndingPoint, Lukla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEndingPoint Context triple: [Three Passes trek, typicalEndingPoint, Lukla]
-
A.
isStartingPointOf
Indicates that something serves as the initial point or origin from which another thing, process, or path begins.
-
B.
typicalEndRelation
chosen
Indicates that one event, state, or process is the usual or characteristic endpoint or outcome of another.
-
C.
finalHomeOf
Indicates that a location is the last or ultimate home, residence, or resting place of an entity.
-
D.
typicalEndDay
Indicates the usual or most common day on which an event, activity, or state typically concludes.
-
E.
typicalConclusion
Indicates that one entity is the usual or expected outcome, result, or ending that follows from another entity or situation.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ffff262fac8190a26ed0577e1860bd |
completed | May 10, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69fffcad7d7c8190a4ad7bb35e33bb75 |
completed | May 10, 2026, 3:34 a.m. |
Created at: April 27, 2026, 4:13 p.m.