Triple
T31175948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hercules |
E794747
|
entity |
| Predicate | nameInRomanMythology |
P91943
|
FINISHED |
| Object | Hercules |
—
|
NE NERFINISHED |
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: Hercules | Statement: [Hercules, nameInRomanMythology, Hercules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameInRomanMythology Context triple: [Hercules, nameInRomanMythology, Hercules]
-
A.
equivalentInRomanMythology
Indicates that one entity corresponds to or is identified as the Roman-mythology counterpart of another entity from a different mythological tradition.
-
B.
epithetOfPantheon
Indicates that one term is used as an epithet or honorific title specifically for a deity or figure within a particular pantheon.
-
C.
equivalentMythologicalName
Indicates that two entities share the same identity in mythology, representing different names or versions of the same mythological figure.
-
D.
praenomenLinkedDeity
Indicates that a person's praenomen (given name) is etymologically or culturally linked to, derived from, or associated with a particular deity.
-
E.
hasMythologicalNamesake
chosen
Indicates that one entity is named after, or shares its name with, a figure or element from mythology.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 9:08 p.m.