Triple
T37681614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penza Regional Drama Theater |
E938247
|
entity |
| Predicate | typicalPerformanceSpace |
P27770
|
FINISHED |
| Object | proscenium stage |
—
|
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: proscenium stage | Statement: [Penza Regional Drama Theater, typicalPerformanceSpace, proscenium stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPerformanceSpace Context triple: [Penza Regional Drama Theater, typicalPerformanceSpace, proscenium stage]
-
A.
typicalPerformance
Indicates the usual or characteristic level at which an entity performs under normal conditions.
-
B.
typicalPerformanceFor
Indicates the usual or characteristic level of performance associated with a given entity, context, or condition.
-
C.
typicalPerformanceElements
Indicates the standard or commonly expected components that characterize how a performance is carried out or evaluated.
-
D.
performanceSpaceType
chosen
Indicates the specific kind or category of space in which a performance or event takes place.
-
E.
typicalPerformanceSetting
Indicates the usual or most common context, venue, or environment in which a performance or activity typically takes place.
- 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.