Triple
T1964516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kroll Opera House, Berlin |
E42657
|
entity |
| Predicate | ceasedOperaPerformances |
P17360
|
FINISHED |
| Object | 1931 |
—
|
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: 1931 | Statement: [Kroll Opera House, Berlin, ceasedOperaPerformances, 1931]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedOperaPerformances Context triple: [Kroll Opera House, Berlin, ceasedOperaPerformances, 1931]
-
A.
hasNotableLivePerformancesBy
Indicates that an entity (such as a work, event, or venue) is associated with notable live performances given by a specified performer or group.
-
B.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, or context.
-
C.
associatedOpera
Indicates that there is a relationship linking an entity to an opera with which it is connected or related (e.g., as subject, inspiration, or context).
-
D.
annualPerformances
Indicates that performances or events occur on a yearly or once-per-year basis.
-
E.
ceasedOperation
chosen
Indicates that an entity has stopped functioning, operating, or carrying out its activities, typically in a permanent or indefinite manner.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3ada4148190ad830d4a3d7fd662 |
completed | March 7, 2026, 5:12 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.