Triple
T26017182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paulinerkirche |
E647054
|
entity |
| Predicate | functionUntilDemolition |
P162907
|
FINISHED |
| Object | concert venue |
—
|
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: concert venue | Statement: [Paulinerkirche, functionUntilDemolition, concert venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionUntilDemolition Context triple: [Paulinerkirche, functionUntilDemolition, concert venue]
-
A.
functionUntilDemolition
chosen
Indicates that an entity continues to serve its intended function or be in active use up to the point in time when it is demolished.
-
B.
aimedToBeDismantledBy
Indicates that one entity was the intended target of dismantling or disassembly by another entity.
-
C.
designedToDestroy
Indicates that one entity was intentionally created or configured for the purpose of damaging, disabling, or annihilating another entity.
-
D.
demolitionEnd
Indicates the point in time or event at which a demolition process is completed or comes to an end.
-
E.
hasDemolitionOrDestruction
Indicates that one entity causes, undergoes, or is associated with the demolition or destruction of 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 22, 2026, 9:03 a.m.