Triple
T6826056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teide Cable Car |
E157017
|
entity |
| Predicate | lowerStation |
P57205
|
FINISHED |
| Object | Base station at approximately 2356 metres |
—
|
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: Base station at approximately 2356 metres | Statement: [Teide Cable Car, lowerStation, Base station at approximately 2356 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerStation Context triple: [Teide Cable Car, lowerStation, Base station at approximately 2356 metres]
-
A.
lowerLocation
Indicates that one entity is located physically below or at a lower vertical position relative to another entity.
-
B.
lowerRank
Indicates that one entity holds an inferior or subordinate rank, status, or position relative to another entity.
-
C.
lowerTerminus
chosen
Indicates that one entity serves as the lower endpoint or downstream terminus of another entity, such as a route, segment, or connection.
-
D.
lowerFieldCharge
Indicates that an entity reduces or decreases the electric charge present in a specified field.
-
E.
lowerCourt
Indicates that one court holds a subordinate or inferior position in the judicial hierarchy relative to another court.
- 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.