Triple
T28527870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thyestes (Seneca) |
E721955
|
entity |
| Predicate | relatedMythologicalCycle |
P9595
|
FINISHED |
| Object | House of Atreus |
—
|
NE NERFINISHED |
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: House of Atreus | Statement: [Thyestes (Seneca), relatedMythologicalCycle, House of Atreus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedMythologicalCycle Context triple: [Thyestes (Seneca), relatedMythologicalCycle, House of Atreus]
-
A.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
B.
subsequentMythology
Indicates that one mythology develops later than, or is derived from, another mythology in time or tradition.
-
C.
centralMythology
Indicates that one entity serves as a core or defining mythological element within the context or tradition of another entity.
-
D.
linkedToMythology
chosen
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
E.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a001540d4f881908a4688881875e774 |
completed | May 10, 2026, 5:18 a.m. |
| PD | Predicate disambiguation | batch_6a0014a8cdd88190a67a90a2df2c5e18 |
completed | May 10, 2026, 5:16 a.m. |
Created at: April 28, 2026, 3:26 a.m.