Triple
T32272726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaza de Mulas base camp |
E824456
|
entity |
| Predicate | typicalApproachDuration |
P7618
|
FINISHED |
| Object | 2 to 3 days trekking 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: 2 to 3 days trekking from trailhead | Statement: [Plaza de Mulas base camp, typicalApproachDuration, 2 to 3 days trekking from trailhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalApproachDuration Context triple: [Plaza de Mulas base camp, typicalApproachDuration, 2 to 3 days trekking from trailhead]
-
A.
typicalDurationDays
chosen
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
B.
typicalDurationMinutes
Indicates the usual or expected length of time, measured in minutes, that an event, activity, or process typically lasts.
-
C.
typicalCompletionTimeInWeeks
Indicates the usual number of weeks it takes to complete the associated task, process, or activity.
-
D.
typicalTestDuration
Indicates the usual or expected length of time required to complete a given test.
-
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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:42 a.m.