Triple
T36162729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yerma (Young Vic production) |
E1045919
|
entity |
| Predicate | usesStagingDevice |
P9919
|
FINISHED |
| Object | glass-box set |
—
|
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: glass-box set | Statement: [Yerma (Young Vic production), usesStagingDevice, glass-box set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStagingDevice Context triple: [Yerma (Young Vic production), usesStagingDevice, glass-box set]
-
A.
stagingDevice
Indicates a relationship where one entity serves as a staging device used to temporarily hold, prepare, or position something for a subsequent process or operation.
-
B.
usesDevice
chosen
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
C.
usedStage
Indicates that an entity made use of a particular stage or phase within a process, workflow, or lifecycle.
-
D.
usesStage
Indicates that one entity employs or operates on another entity at a particular phase or stage within a process or workflow.
-
E.
usesStageType
Indicates that one entity employs or operates with a particular type or category of stage.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: May 3, 2026, 4:08 p.m.