Triple
T28039609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titlis |
E708500
|
entity |
| Predicate | hasCableCarType |
P121369
|
FINISHED |
| Object | rotating gondola |
—
|
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: rotating gondola | Statement: [Titlis, hasCableCarType, rotating gondola]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCableCarType Context triple: [Titlis, hasCableCarType, rotating gondola]
-
A.
hasCableCar
Indicates that one entity possesses, operates, or is served by a cable car system connecting it to other locations or points.
-
B.
cablewayType
chosen
Indicates the specific kind or classification of a cableway system associated with an entity.
-
C.
cableCarSystem
Indicates a relationship where a transportation system operates vehicles pulled by cables along fixed routes, typically on steep gradients.
-
D.
hasFunicular
Indicates that one place or facility is equipped with or served by a funicular railway connection to another location.
-
E.
cableCarSystemBuiltIn
Indicates that a cable car system was constructed or established within a specific location or context.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 27, 2026, 8:24 p.m.