Triple
T4610035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedroom Farce |
E100530
|
entity |
| Predicate | typicalProductionStyle |
P56743
|
FINISHED |
| Object | proscenium staging |
—
|
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 staging | Statement: [Bedroom Farce, typicalProductionStyle, proscenium staging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProductionStyle Context triple: [Bedroom Farce, typicalProductionStyle, proscenium staging]
-
A.
typicalProductionType
Indicates the usual or characteristic type of production activity associated with an entity.
-
B.
usesProductionStyle
chosen
Indicates that one entity creates, presents, or operates another entity using a particular production style or method.
-
C.
typicalPractice
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
-
D.
traditionalProductionArea
Indicates that something originates from or is associated with a region historically recognized for producing it according to established traditions.
-
E.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
- 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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59be3300819095e548b488c8f75e |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.