Triple
T25420759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | fatherhood of Orpheus |
E636976
|
entity |
| Predicate | connectedToMythCycle |
P37306
|
FINISHED |
| Object | Orphic myths |
—
|
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: Orphic myths | Statement: [fatherhood of Orpheus, connectedToMythCycle, Orphic myths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToMythCycle Context triple: [fatherhood of Orpheus, connectedToMythCycle, Orphic myths]
-
A.
dedicatedCycleTo
Indicates that a particular cycle, period, or iteration is specifically allocated or reserved for a given purpose, task, or entity.
-
B.
connectsAtStation
Indicates that one transportation service or route links to another at a specific station, allowing passengers to transfer between them there.
-
C.
connectionTo
chosen
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
D.
connectedToBySaddle
Indicates that two entities are linked or joined together specifically via a saddle-like structure or connection.
-
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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 21, 2026, 1:56 p.m.