Triple
T30294348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stok Kangri |
E770473
|
entity |
| Predicate | approachDurationFromLeh |
P40755
|
FINISHED |
| Object | about 2 days to base camp |
—
|
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: about 2 days to base camp | Statement: [Stok Kangri, approachDurationFromLeh, about 2 days to base camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachDurationFromLeh Context triple: [Stok Kangri, approachDurationFromLeh, about 2 days to base camp]
-
A.
directionFromLeh
Indicates the directional relationship of an entity or location as measured or described relative to Leh.
-
B.
hasApproachLength
Indicates that one entity has a specified length associated with its approach or access path to another entity.
-
C.
intendedDuration
chosen
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
D.
hasApproachTime
Indicates that an entity is associated with a specific time at which it approaches or comes near another entity or location.
-
E.
evaDuration
Indicates the length of time that an extravehicular activity (EVA) lasts or is scheduled to last.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 29, 2026, 7:47 p.m.