Triple
T33049618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Atossa |
E845687
|
entity |
| Predicate | dramaticThemeAssociation |
P73134
|
FINISHED |
| Object | hubris of imperial power |
—
|
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: hubris of imperial power | Statement: [Queen Atossa, dramaticThemeAssociation, hubris of imperial power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dramaticThemeAssociation Context triple: [Queen Atossa, dramaticThemeAssociation, hubris of imperial power]
-
A.
dramaticTheme
chosen
Indicates that a work, scene, or narrative centers around a particular dramatic subject, motif, or emotional conflict as its main thematic focus.
-
B.
theatricalSubject
Indicates that an entity serves as the main focus, topic, or subject within a theatrical work, performance, or dramatic context.
-
C.
majorThemeAssociation
Indicates that one entity is associated with another as a primary or central theme.
-
D.
filmThemeConnection
Indicates a relationship where a film is associated with, explores, or is centered around a particular theme.
-
E.
theatricalGenre
Indicates the specific theatrical genre or style to which a performance, play, or production belongs.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:24 a.m.