Triple
T8713034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zugspitzplatt |
E206825
|
entity |
| Predicate | hasCableCarConnection |
P8378
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Zugspitzplatt, hasCableCarConnection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCableCarConnection Context triple: [Zugspitzplatt, hasCableCarConnection, yes]
-
A.
hasCableCar
chosen
Indicates that one entity possesses, operates, or is served by a cable car system connecting it to other locations or points.
-
B.
hasSkiLiftConnectionTo
Indicates a relationship where one location is directly connected to another by a ski lift, allowing travel between them via that lift.
-
C.
hasSkiLiftConnectionWith
Indicates a relationship where two locations or areas are directly connected by a ski lift that allows travel between them.
-
D.
cableCarSystem
Indicates a relationship where a transportation system operates vehicles pulled by cables along fixed routes, typically on steep gradients.
-
E.
hasPassengerRailConnection
Indicates that there exists a passenger rail service linking one location or transport node to another.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cd522a88190a32facd86206af66 |
completed | March 31, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.