Triple
T20403919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tunic of Heracles |
E500410
|
entity |
| Predicate | intendedUseByDeianeira |
P140010
|
FINISHED |
| Object | love charm |
—
|
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: love charm | Statement: [tunic of Heracles, intendedUseByDeianeira, love charm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedUseByDeianeira Context triple: [tunic of Heracles, intendedUseByDeianeira, love charm]
-
A.
relationshipToDeianira
Indicates a specified type of relationship that one entity has to Deianira, such as familial, romantic, or social connection.
-
B.
goalInTrojanWar
Indicates that an entity’s objective, aim, or purpose is specifically directed toward or realized within the context of the Trojan War.
-
C.
HeraBribe
Indicates that Hera offers something of value as a bribe to influence or persuade another entity to act in her favor.
-
D.
AphroditeBribe
Indicates that one entity (Aphrodite) offers or gives a persuasive incentive or reward to another entity in order to influence their decision or allegiance.
-
E.
roleInTrojanWar
Indicates the specific function, position, or part an entity played in the events of the Trojan War.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6799080cc819096dc31f41d1d7b49 |
completed | April 20, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:29 a.m.