Triple
T31937316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Children of Medea |
E815425
|
entity |
| Predicate | firstMajorLiterarySource |
P10578
|
FINISHED |
| Object | Medea by Euripides |
E200045
|
NE 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: Medea by Euripides | Statement: [Children of Medea, firstMajorLiterarySource, Medea by Euripides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorLiterarySource Context triple: [Children of Medea, firstMajorLiterarySource, Medea by Euripides]
-
A.
firstMajorLiteraryAppearanceAuthor
Indicates the author responsible for the work in which an entity made its first major literary appearance.
-
B.
firstMajorPublication
Indicates the relationship where a work is the earliest significant publication associated with an entity (such as a person or organization).
-
C.
literarySource
chosen
Indicates that one entity serves as the written or literary origin, reference, or basis for another entity.
-
D.
firstMajorLiteraryUseDate
Indicates the date when something was first significantly used or attested in major literary works.
-
E.
hasLaterLiterarySource
Indicates that a work or text serves as a literary source that appears later in time than another related work or text.
- F. None of above.
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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34703015988190842130e92024d920 |
completed | June 18, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:05 a.m.