Triple
T23662667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danaids |
E584492
|
entity |
| Predicate | areConnectedToMythCycle |
P9998
|
FINISHED |
| Object | myths of Argos |
—
|
LITERAL 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: myths of Argos | Statement: [Danaids, areConnectedToMythCycle, myths of Argos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areConnectedToMythCycle Context triple: [Danaids, areConnectedToMythCycle, myths of Argos]
-
A.
coreMyth
Indicates that something constitutes a central, foundational myth within a belief system, narrative, or cultural tradition.
-
B.
hasPlatformsConnectedBy
Indicates that two or more platforms are linked together by some connecting structure or mechanism.
-
C.
hasMythSource
Indicates that something derives from, is based on, or is supported by a particular myth or mythological source.
-
D.
hasMythType
chosen
Indicates that an entity is associated with or classified under a particular type or category of myth.
-
E.
hasCupConnection
Indicates that there is a functional or physical connection involving a cup between the related entities.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4094c448190be12402422451e89 |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.