Triple
T13362915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point Lenana |
E318862
|
entity |
| Predicate | typicalTotalTrekDuration |
P106942
|
FINISHED |
| Object | 3–5 days round trip |
—
|
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: 3–5 days round trip | Statement: [Point Lenana, typicalTotalTrekDuration, 3–5 days round trip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTotalTrekDuration Context triple: [Point Lenana, typicalTotalTrekDuration, 3–5 days round trip]
-
A.
trekDurationApprox
chosen
Indicates an approximate length of time that the trek is expected to take.
-
B.
typicalTourDuration
Indicates the usual length of time that a tour normally takes to complete.
-
C.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
D.
durationTypicalAscent
Indicates the typical amount of time required to complete an ascent.
-
E.
dayOfTrek
Indicates the specific day or stage within a multi-day trek on which an event, action, or condition occurs.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69da628affd081909f1790d333f0eef4 |
completed | April 11, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.