Triple
T26641267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kangchenjunga Base Camp trekking route |
E668784
|
entity |
| Predicate | approximateDurationDays |
P172309
|
FINISHED |
| Object | 18 |
—
|
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: 18 | Statement: [Kangchenjunga Base Camp trekking route, approximateDurationDays, 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDurationDays Context triple: [Kangchenjunga Base Camp trekking route, approximateDurationDays, 18]
-
A.
durationDaysApprox
chosen
Indicates an approximate length of time, measured in days, for which an event, state, or condition lasts.
-
B.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
C.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
D.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
E.
commonDuration
Indicates that two or more events, actions, or states share the same length of time.
- 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 27, 2026, 2:29 a.m.