Triple
T22678352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eight Songs for a Mad King |
E560408
|
entity |
| Predicate | theatricalElements |
P149209
|
FINISHED |
| Object | spoken voice |
—
|
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: spoken voice | Statement: [Eight Songs for a Mad King, theatricalElements, spoken voice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theatricalElements Context triple: [Eight Songs for a Mad King, theatricalElements, spoken voice]
-
A.
theatricalSubject
Indicates that an entity serves as the main focus, topic, or subject within a theatrical work, performance, or dramatic context.
-
B.
theatricalContext
Indicates the situational or environmental circumstances related to a theatrical performance or production in which an action or relationship occurs.
-
C.
theatricalSetting
Indicates the spatial or contextual environment in which a theatrical performance or dramatic action takes place.
-
D.
theatricalSignificance
Indicates that something holds notable importance, impact, or relevance within a theatrical or stage-performance context.
-
E.
partOfTheatre
Indicates that one entity is a component, section, or subdivision of a theatre.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1785e4e7481909f1ebd6d8dbd6585 |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:11 p.m.