Triple
T28039758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engelberg-Titlis ski area |
E708504
|
entity |
| Predicate | hasTopStation |
P178592
|
FINISHED |
| Object | Klein Titlis |
—
|
NE NERFINISHED |
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: Klein Titlis | Statement: [Engelberg-Titlis ski area, hasTopStation, Klein Titlis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopStation Context triple: [Engelberg-Titlis ski area, hasTopStation, Klein Titlis]
-
A.
hasEndpointStation
Indicates that something (such as a route, line, or service) has a specific station as one of its terminal endpoints.
-
B.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
C.
hasLowerStationAt
Indicates that one entity has a subordinate or lower-ranked position relative to another entity within a hierarchical structure.
-
D.
hasLowerStation
Indicates that one entity occupies a lower rank, status, or position in a hierarchy relative to another entity.
-
E.
hasInterchangeStationWith
Indicates that two transportation lines, routes, or systems share a station where passengers can transfer between them.
- F. None of above. chosen
Provenance (4 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_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f7117cf2188190b29e36fc1e342c60 |
completed | May 3, 2026, 9:12 a.m. |
Created at: April 27, 2026, 8:24 p.m.