Triple
T4771400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinrich-Hertz-Turm |
E105933
|
entity |
| Predicate | structureSystem |
P33532
|
FINISHED |
| Object | concrete shaft tower |
—
|
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: concrete shaft tower | Statement: [Heinrich-Hertz-Turm, structureSystem, concrete shaft tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structureSystem Context triple: [Heinrich-Hertz-Turm, structureSystem, concrete shaft tower]
-
A.
buildingSystem
chosen
Indicates that one entity functions as a system, subsystem, or organized set of components that serves or supports the operation of a building.
-
B.
buildingStructure
Indicates that one entity is a structural component or physical part that forms, supports, or constitutes the construction of another entity.
-
C.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
D.
rootStructure
Indicates that one entity serves as the primary or foundational structural element upon which another entity is based or organized.
-
E.
structureStyle
Indicates the architectural or design style characterizing how a structure is built or formed.
- 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.