Triple
T6826058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teide Cable Car |
E157017
|
entity |
| Predicate | accessToTrails |
P8966
|
FINISHED |
| Object | trail to Teide summit (with permit) |
—
|
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: trail to Teide summit (with permit) | Statement: [Teide Cable Car, accessToTrails, trail to Teide summit (with permit)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessToTrails Context triple: [Teide Cable Car, accessToTrails, trail to Teide summit (with permit)]
-
A.
TrailLinkIs
Indicates that one trail segment is connected to or continues from another trail segment.
-
B.
trailblazerFor
Indicates that one entity serves as a pioneering example, opening the way or setting a precedent for another entity to follow or build upon.
-
C.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
D.
hasTrailheads
Indicates that one location or area contains or provides access points where trails begin.
-
E.
recreationAccess
chosen
Indicates that one entity provides or has the ability to use recreational facilities, activities, or spaces associated with another 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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d58375248190935dd38d618994e3 |
completed | March 27, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.