Triple
T2746510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulm Minster |
E60881
|
entity |
| Predicate | heightToObservationPlatform |
P5396
|
FINISHED |
| Object | approximately 143 metres |
—
|
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: approximately 143 metres | Statement: [Ulm Minster, heightToObservationPlatform, approximately 143 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heightToObservationPlatform Context triple: [Ulm Minster, heightToObservationPlatform, approximately 143 metres]
-
A.
observationDeckHeight
chosen
Indicates the vertical distance of an observation deck above a reference level, typically the ground or sea level.
-
B.
hasViewingPlatform
Indicates that an entity includes or is equipped with a designated platform or area intended for viewing or observing something.
-
C.
platformHeight
Indicates the vertical distance or elevation of a platform relative to a defined reference level.
-
D.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
E.
heightWithPedestal
Indicates the total vertical measurement of an object including the height of its supporting pedestal.
- 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_69ab4b79846081909096725374d65ce9 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb4ed6bc8190876c1d188b97692b |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd829f1e88190aab1d54f87c69714 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.