Triple
T32272665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaza de Mulas route |
E824455
|
entity |
| Predicate | startsAtTrailhead |
P191752
|
FINISHED |
| Object | Horcones entrance of Aconcagua Provincial Park |
—
|
NE NERFINISHED |
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: Horcones entrance of Aconcagua Provincial Park | Statement: [Plaza de Mulas route, startsAtTrailhead, Horcones entrance of Aconcagua Provincial Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startsAtTrailhead Context triple: [Plaza de Mulas route, startsAtTrailhead, Horcones entrance of Aconcagua Provincial Park]
-
A.
trailheadIn
Indicates that a trailhead is located within or at a specific place or area.
-
B.
reachedFromTrailhead
Indicates that a location or point can be accessed by traveling from a designated trailhead.
-
C.
hasTrailheadAt
Indicates that a trail or route begins or has its official starting point at a specified location.
-
D.
hasTrailheadSignage
Indicates that a trailhead is equipped with signage providing information or guidance to users.
-
E.
trailStartsFrom
chosen
Indicates that the starting point or origin of a trail is located at a specified place or entity.
- 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_69ff6a4ce9a08190b98abde3a170dd69 |
completed | May 9, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69ff69c11634819089d1084bd2c11534 |
completed | May 9, 2026, 5:07 p.m. |
Created at: May 1, 2026, 12:42 a.m.