Triple

T37317055
Position Surface form Disambiguated ID Type / Status
Subject Temple of Hercules Musarum E926364 entity
Predicate deityRoleOfHercules P118406 FINISHED
Object hero and god associated with strength 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 and god associated with strength | Statement: [Temple of Hercules Musarum, deityRoleOfHercules, hero and god associated with strength]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: deityRoleOfHercules
Context triple: [Temple of Hercules Musarum, deityRoleOfHercules, hero and god associated with strength]
  • A. mythologicalRole
    Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
  • B. roleOfReferencedDeity chosen
    Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
  • C. relationshipToHeracles
    Indicates the specific familial or social relationship that an entity has to Heracles.
  • D. HerculesLintonRole
    Indicates that a specified role or function is held or performed by Hercules Linton in a given context.
  • 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_69f76eb28af88190b093b32e3fd614ab completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb78cbef988190b8f79d946b46e6b2 completed May 6, 2026, 5:22 p.m.
PD Predicate disambiguation batch_69fb5a9ac5a08190b24ef308963fc52b completed May 6, 2026, 3:13 p.m.
Created at: May 3, 2026, 4:16 p.m.