Triple
T19941817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euripides’ lost play "Antigone" |
E479323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | lost ancient Greek tragedy |
C773
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: lost ancient Greek tragedy Context triple: [Euripides’ lost play "Antigone", instanceOf, lost ancient Greek tragedy]
-
A.
ancient Greek theatre
Ancient Greek theatre is a classical performance tradition combining drama, music, and dance in large open-air amphitheaters, used for religious festivals, civic engagement, and storytelling through tragedy, comedy, and satyr plays.
-
B.
tragedy
chosen
Tragedy is a dramatic or narrative form in which a protagonist, often of high status or noble character, is brought to ruin or profound suffering through a combination of personal flaws, fate, and unavoidable circumstances, evoking pity and fear in the audience.
-
C.
ancient Greek literature
Ancient Greek literature encompasses the epic, lyric, dramatic, historical, and philosophical writings produced in the Greek language from the archaic through the Hellenistic periods, foundational to Western literary and intellectual traditions.
-
D.
tragédie lyrique
Tragédie lyrique is a French Baroque operatic genre that combines serious mythological or heroic subjects with music, dance, and elaborate staging, typically structured in a prologue and five acts.
-
E.
tragedy trilogy
A tragedy trilogy is a set of three thematically or narratively linked tragic works that together depict a progression of suffering, conflict, and often catastrophic resolution.
- F. None of above.
Provenance (1 batch)
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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:54 p.m.