Triple
T8347766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Hippolyta |
E196082
|
entity |
| Predicate | questObjectOf |
P24308
|
FINISHED |
| Object | Heracles' labor to obtain her girdle |
—
|
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: Heracles' labor to obtain her girdle | Statement: [Queen Hippolyta, questObjectOf, Heracles' labor to obtain her girdle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questObjectOf Context triple: [Queen Hippolyta, questObjectOf, Heracles' labor to obtain her girdle]
-
A.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
-
B.
questedBy
Indicates that a quest or mission is initiated, assigned, or undertaken by a particular entity.
-
C.
questInvolvedIn
Indicates that an entity participates in, is associated with, or plays a role in a particular quest or mission.
-
D.
expeditionObjective
chosen
Indicates the primary goal or purpose that an expedition is intended to achieve.
-
E.
hasRitualObject
Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial context.
- 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_69ca82edd63c8190b876b8465464c5fa |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb801588e881908ac0a291280ac0f8 |
completed | March 31, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:58 p.m.