Triple
T21069374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hercules and Antaeus |
E519062
|
entity |
| Predicate | narrativeRoleOfHeracles |
P9987
|
FINISHED |
| Object | hero |
—
|
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: hero | Statement: [Hercules and Antaeus, narrativeRoleOfHeracles, hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeRoleOfHeracles Context triple: [Hercules and Antaeus, narrativeRoleOfHeracles, hero]
-
A.
relationshipToHeracles
Indicates the specific familial or social relationship that an entity has to Heracles.
-
B.
mythologicalRole
chosen
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
C.
childWithHeracles
Indicates that one entity is a child whose father is Heracles.
-
D.
associatedEpicHero
Indicates a relationship where one entity is linked to, or thematically connected with, a particular epic hero.
-
E.
roleAfterHeraclesDeath
Indicates the role or position an entity assumes or holds following the death of Heracles.
- 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb6d3a081909d6a6b181786deff |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:46 p.m.