Triple
T12274634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead Woman’s Pass |
E292557
|
entity |
| Predicate | dayOfTrek |
P104180
|
FINISHED |
| Object | typically reached on the second day of the classic four-day Inca Trail |
—
|
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: typically reached on the second day of the classic four-day Inca Trail | Statement: [Dead Woman’s Pass, dayOfTrek, typically reached on the second day of the classic four-day Inca Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dayOfTrek Context triple: [Dead Woman’s Pass, dayOfTrek, typically reached on the second day of the classic four-day Inca Trail]
-
A.
hikeLength
Indicates the distance or duration associated with a hiking activity or trail.
-
B.
durationTypicalAscent
Indicates the typical amount of time required to complete an ascent.
-
C.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
D.
isHikingTrail
Indicates that a path or route is designated and used specifically for hiking activities.
-
E.
firstAscentDurationDays
Indicates the number of days taken to complete the first ascent of something.
- F. None of above. chosen
Provenance (4 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d93805cee08190a532ebcf5908e617 |
completed | April 10, 2026, 5:48 p.m. |
Created at: April 8, 2026, 9:52 p.m.