Triple
T31937203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corinth (in the Jason–Medea narrative) |
E815423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | setting in Greek tragedy |
C59501
|
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: setting in Greek tragedy Context triple: [Corinth (in the Jason–Medea narrative), instanceOf, setting in Greek tragedy]
-
A.
element of ancient Greek tragedy
An element of ancient Greek tragedy is a fundamental component—such as plot, character, diction, thought, spectacle, or song—that together shapes the dramatic structure and emotional impact of the play.
-
B.
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.
-
C.
Euripides character
A Euripides character is a dramatic figure from the plays of the ancient Greek tragedian Euripides, often marked by psychological complexity, moral ambiguity, and intense emotional conflict.
-
D.
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.
-
E.
character in ancient Greek comedy
A character in ancient Greek comedy is a typically exaggerated, often stock figure whose humorous actions, dialogue, and social role serve to satirize contemporary customs, politics, and human follies within the structure of a comic play.
- F. None of above. chosen
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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:05 a.m.