Triple
T4309213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stubaital |
E94030
|
entity |
| Predicate | hasSportInfrastructure |
P6792
|
FINISHED |
| Object | cable cars |
—
|
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: cable cars | Statement: [Stubaital, hasSportInfrastructure, cable cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSportInfrastructure Context triple: [Stubaital, hasSportInfrastructure, cable cars]
-
A.
hasSportsGround
Indicates that an entity possesses, includes, or is associated with a sports ground or athletic field as part of its facilities or area.
-
B.
hasRecreationFacility
chosen
Indicates that one entity provides, contains, or is equipped with a recreational facility for use by another entity or by the public.
-
C.
hasCommercialInfrastructure
Indicates that an entity possesses or is equipped with facilities, systems, or structures that support commercial or business activities.
-
D.
hasSportsService
Indicates that an entity provides or is associated with a sports-related service.
-
E.
hasSportsVenueType
Indicates that a sports venue is classified as being of a specific type or category (e.g., stadium, arena, 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350d40748819084798058396be113 |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:11 p.m.