Triple
T28039759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engelberg-Titlis ski area |
E708504
|
entity |
| Predicate | hasBaseStation |
P26804
|
FINISHED |
| Object | Engelberg village |
—
|
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: Engelberg village | Statement: [Engelberg-Titlis ski area, hasBaseStation, Engelberg village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseStation Context triple: [Engelberg-Titlis ski area, hasBaseStation, Engelberg village]
-
A.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
B.
hasNearbyBase
chosen
Indicates that one entity has a base or facility located in close physical proximity to another entity or location.
-
C.
hasStationNear
Indicates that one entity has a station located in close proximity to another entity.
-
D.
hasStationFunction
Indicates that an entity serves in a particular functional role or capacity at a station.
-
E.
hasStationManagement
Indicates that one entity is responsible for managing, operating, or overseeing the activities and administration of a station associated with another entity.
- 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_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 8:24 p.m.