Triple
T20643062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Town Hall (Hanover) |
E507278
|
entity |
| Predicate | viewingPlatformHeight |
P5396
|
FINISHED |
| Object | about 97 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: about 97 metres | Statement: [New Town Hall (Hanover), viewingPlatformHeight, about 97 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewingPlatformHeight Context triple: [New Town Hall (Hanover), viewingPlatformHeight, about 97 metres]
-
A.
platformHeight
Indicates the vertical distance or elevation of a platform relative to a defined reference level.
-
B.
hasViewingPlatform
Indicates that an entity includes or is equipped with a designated platform or area intended for viewing or observing something.
-
C.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
D.
observationDeckHeight
chosen
Indicates the vertical distance of an observation deck above a reference level, typically the ground or sea level.
-
E.
platformLength
Indicates that one entity specifies the physical length or extent of a platform 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_69e0b4be702c8190a3d2410a881d310a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6af1c51f48190abba54a5aace9fc8 |
completed | April 20, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.