Triple
T11764430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venetian theatres |
E279744
|
entity |
| Predicate | stageTechnology |
P101251
|
FINISHED |
| Object | complex stage machinery |
—
|
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: complex stage machinery | Statement: [Venetian theatres, stageTechnology, complex stage machinery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageTechnology Context triple: [Venetian theatres, stageTechnology, complex stage machinery]
-
A.
stageConfiguration
Indicates the specific arrangement or setup of components, elements, or conditions at a particular stage within a process or system.
-
B.
stageDesigner
Indicates that one entity is responsible for designing or creating the stage or set for a performance or event in relation to another entity.
-
C.
stage
Indicates that an entity organizes, presents, or performs another entity (such as an event, show, or action) as a staged occurrence.
-
D.
stageProduction
Indicates that an entity organizes and presents a live performance or show, typically involving planning, rehearsing, and mounting the production for an audience.
-
E.
stageName
Indicates that one entity is the performance or professional name used by another entity.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a5248e0881909ed1b4df7be422f7 |
completed | April 10, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69d88a829fe481909cc5431de7d6058e |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890467a2481909ce6c669e739c8de |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.