Triple
T6826043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teide Cable Car |
E157017
|
entity |
| Predicate | summitProximity |
P45695
|
FINISHED |
| Object | about 200 metres below Teide summit |
—
|
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 200 metres below Teide summit | Statement: [Teide Cable Car, summitProximity, about 200 metres below Teide summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitProximity Context triple: [Teide Cable Car, summitProximity, about 200 metres below Teide summit]
-
A.
summitEnvironment
Indicates the environmental conditions or context present at the summit of a mountain or peak.
-
B.
summitAccessibleFrom
Indicates that a summit can be reached or accessed starting from a specified location or route.
-
C.
summitDepth
Indicates the vertical distance from a summit’s highest point down to a specified reference level, such as a base or surrounding terrain.
-
D.
hasSummitCountApprox
Indicates that an entity is associated with an approximate number of summits or peak ascents.
-
E.
isCloseTo
chosen
Indicates that one entity is physically or conceptually near another, within a relatively short distance or range.
- 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.