Triple
T21848325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scholia on Euripides and other later mythographic sources |
E539435
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | secondary source on Greek mythology |
C1980
|
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: secondary source on Greek mythology Context triple: [Scholia on Euripides and other later mythographic sources, instanceOf, secondary source on Greek mythology]
-
A.
reference work on Greek mythology
A reference work on Greek mythology is a comprehensive, systematically organized resource that summarizes, explains, and cross-references the gods, heroes, creatures, places, and narratives of ancient Greek mythic tradition.
-
B.
ancient Greek mythographical handbook
An ancient Greek mythographical handbook is a concise reference work that systematically compiles, organizes, and summarizes traditional myths, genealogies, and heroic tales for consultation and instruction.
-
C.
mythology
Mythology is a body of traditional stories, beliefs, and legends that cultures use to explain natural phenomena, human behavior, and the origins of the world and their customs.
-
D.
mythographical compendium
chosen
A mythographical compendium is a curated collection of myths, legends, and related commentary that systematically organizes and interprets traditional narratives from one or more cultures.
-
E.
mythological text
A mythological text is a written work that records, interprets, or retells traditional myths, deities, and cosmological narratives of a culture, often explaining origins, values, and supernatural events.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:55 p.m.