Triple
T4771399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinrich-Hertz-Turm |
E105933
|
entity |
| Predicate | publicAccessToObservationDeck |
P42850
|
FINISHED |
| Object | suspended |
—
|
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: suspended | Statement: [Heinrich-Hertz-Turm, publicAccessToObservationDeck, suspended]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicAccessToObservationDeck Context triple: [Heinrich-Hertz-Turm, publicAccessToObservationDeck, suspended]
-
A.
hasObservationDeckAccess
chosen
Indicates that an entity is permitted to enter or use an observation deck.
-
B.
publicObservationDeck
Indicates a relationship where a location serves as an observation deck that is accessible for use by the general public.
-
C.
hasObservationDeckName
Indicates that an observation deck is associated with a specific name or title.
-
D.
observationDeckHeight
Indicates the vertical distance of an observation deck above a reference level, typically the ground or sea level.
-
E.
observationDeckFloor
Indicates the specific floor or level of a building on which an observation deck is located.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd655e5dcc8190a932be9b1baaffb2 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.