Triple
T36332111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaispeicher A |
E894677
|
entity |
| Predicate | foundationRetainedIn |
P199137
|
FINISHED |
| Object | Elbphilharmonie |
—
|
NE NERFINISHED |
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: Elbphilharmonie | Statement: [Kaispeicher A, foundationRetainedIn, Elbphilharmonie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundationRetainedIn Context triple: [Kaispeicher A, foundationRetainedIn, Elbphilharmonie]
-
A.
foundation
Indicates that one entity serves as the base, support, or underlying basis upon which another entity is built, established, or depends.
-
B.
foundationStatus
Indicates the current legal or operational state of a foundation, such as whether it is active, inactive, pending, or dissolved.
-
C.
foundationEvent
Indicates the event or act through which something (such as an organization, institution, or structure) is formally established or created.
-
D.
foundationType
Indicates the structural or organizational basis on which something is built, established, or supported.
-
E.
providedFoundationFor
Indicates that one entity served as the essential basis, support, or groundwork enabling the existence, development, or success of another entity or outcome.
- F. None of above. chosen
Provenance (4 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_69f76e4dcf088190a6c3216c209cab52 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
| PDg | Predicate description generation | batch_69ff21ca6964819088bdf1810b7863f2 |
completed | May 9, 2026, noon |
Created at: May 3, 2026, 4:09 p.m.