Triple
T25420734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oeagrus of Thrace |
E636975
|
entity |
| Predicate | roleInOrpheusMyth |
P9987
|
FINISHED |
| Object | biological father of Orpheus |
—
|
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: biological father of Orpheus | Statement: [Oeagrus of Thrace, roleInOrpheusMyth, biological father of Orpheus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInOrpheusMyth Context triple: [Oeagrus of Thrace, roleInOrpheusMyth, biological father of Orpheus]
-
A.
mythologicalRole
chosen
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
B.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
C.
roleWithDionysus
Indicates a role, association, or functional relationship that an entity has in connection with Dionysus.
-
D.
roleInAnalects
Indicates that one entity has a specific role, function, or status within the context of the Analects.
-
E.
roleInTauris
Indicates that an entity has a specific role or function within the context of Tauris (e.g., a work, setting, or domain associated with Tauris).
- 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_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 21, 2026, 1:56 p.m.