Triple
T5106807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyllus |
E115114
|
entity |
| Predicate | fulfilledWish |
P61605
|
FINISHED |
| Object | married Iole at Heracles’ command |
—
|
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: married Iole at Heracles’ command | Statement: [Hyllus, fulfilledWish, married Iole at Heracles’ command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fulfilledWish Context triple: [Hyllus, fulfilledWish, married Iole at Heracles’ command]
-
A.
promiseOfBlessingTo
Indicates that one entity has declared or assured a future blessing or favorable outcome to another entity.
-
B.
blessedBy
Indicates that one entity has conferred a blessing, favor, or sacred endorsement upon another entity.
-
C.
enchantedBy
Indicates that one entity has cast or holds a magical enchantment over another entity.
-
D.
miracleType
Indicates the specific category or kind of miracle associated with an event or entity.
-
E.
miraclePerformedBy
Indicates that a miraculous event is carried out or caused by a particular agent or entity.
- F. None of above. chosen
Provenance (4 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_69bd4440b3348190be1251fd8b7951f1 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75a8ee7881908876859402911e5a |
completed | March 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd72e1b7cc8190b2e621fdf8f22e38 |
completed | March 20, 2026, 4:16 p.m. |
Created at: March 20, 2026, 1:41 p.m.