Triple
T1964508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kroll Opera House, Berlin |
E42657
|
entity |
| Predicate | parliamentSessionsHeldFrom |
P33289
|
FINISHED |
| Object | 1933 |
—
|
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: 1933 | Statement: [Kroll Opera House, Berlin, parliamentSessionsHeldFrom, 1933]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentSessionsHeldFrom Context triple: [Kroll Opera House, Berlin, parliamentSessionsHeldFrom, 1933]
-
A.
hasLegislativeSessionCount
Indicates the number of legislative sessions associated with a given legislative body, term, or jurisdiction.
-
B.
servedInParliamentFor
Indicates that a person held a parliamentary seat as a representative of a specified constituency, region, or jurisdiction.
-
C.
hasPlenarySessions
Indicates that an event or organization includes formal plenary sessions as part of its activities or structure.
-
D.
parliamentaryTerm
Indicates the specific legislative session or fixed period of time during which a parliament is formally in office and exercises its authority.
-
E.
legislativePeriod
Indicates the specific legislative term or session during which an action, event, or status is valid or took place.
- 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_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. |
| PDg | Predicate description generation | batch_69abb16a6db48190af04012e8ed2269f |
completed | March 7, 2026, 5:02 a.m. |
Created at: March 4, 2026, 7:36 p.m.