Triple
T5208259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bavarian State Opera |
E117564
|
entity |
| Predicate | mainVenueRebuilt |
P11204
|
FINISHED |
| Object | after World War II |
—
|
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: after World War II | Statement: [Bavarian State Opera, mainVenueRebuilt, after World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainVenueRebuilt Context triple: [Bavarian State Opera, mainVenueRebuilt, after World War II]
-
A.
replacedVenue
Indicates that one venue has taken the place of another as its successor location or site.
-
B.
previousVenue
Indicates that one venue was used or occupied before another in a sequence of venues.
-
C.
largelyRebuilt
chosen
Indicates that an entity has been substantially reconstructed or renovated, with most of its original structure replaced or significantly altered.
-
D.
reopenedAsConcertHall
Indicates that a previously closed or differently purposed venue has been opened again specifically to function as a concert hall.
-
E.
rebuildPlace
Indicates that an entity restores or reconstructs a place that was previously damaged, destroyed, or altered.
- 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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a6d70d081908c74e86b3bca9ba2 |
completed | March 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.