Triple
T25007055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of Knives |
E625869
|
entity |
| Predicate | theatricality |
P149209
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Queen of Knives, theatricality, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theatricality Context triple: [Queen of Knives, theatricality, high]
-
A.
theatricalSignificance
Indicates that something holds notable importance, impact, or relevance within a theatrical or stage-performance context.
-
B.
theatricalElements
chosen
Indicates the presence or use of components related to theater or performance (such as staging, acting, or dramatic techniques) within or between the associated entities.
-
C.
theatricalContext
Indicates the situational or environmental circumstances related to a theatrical performance or production in which an action or relationship occurs.
-
D.
theatricalSetting
Indicates the spatial or contextual environment in which a theatrical performance or dramatic action takes place.
-
E.
theatricalSubject
Indicates that an entity serves as the main focus, topic, or subject within a theatrical work, performance, or dramatic context.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44b12bd788190bc32bb8129c4550e |
completed | May 1, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:05 a.m.