Triple
T5455848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cadmus et Hermione |
E122474
|
entity |
| Predicate | usesMythologicalPrologue |
P60508
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cadmus et Hermione, usesMythologicalPrologue, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMythologicalPrologue Context triple: [Cadmus et Hermione, usesMythologicalPrologue, true]
-
A.
usesMythOf
chosen
Indicates that one entity employs or invokes a myth or mythical narrative about another entity as part of its actions, explanations, or representations.
-
B.
originMyth
Indicates the traditional myth or legendary narrative that explains the beginnings or creation of a people, place, institution, or phenomenon.
-
C.
settingOfMyth
Indicates that a location or environment serves as the backdrop or context in which a particular myth takes place.
-
D.
hasMythologicalFeature
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
-
E.
mythologicalEvent
Indicates an event or occurrence that takes place within mythological narratives or traditions, often involving gods, heroes, or supernatural phenomena.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.