Triple

T7398716
Position Surface form Disambiguated ID Type / Status
Subject Peleus E170690 entity
Predicate hasMythologicalEpisode P2288 FINISHED
Object accidental killing of Eurytion 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: accidental killing of Eurytion | Statement: [Peleus, hasMythologicalEpisode, accidental killing of Eurytion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMythologicalEpisode
Context triple: [Peleus, hasMythologicalEpisode, accidental killing of Eurytion]
  • A. hasMythologicalFeature
    Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
  • B. mythologicalEvent chosen
    Indicates an event or occurrence that takes place within mythological narratives or traditions, often involving gods, heroes, or supernatural phenomena.
  • C. hasMythologicalOpponents
    Indicates that one entity is opposed or challenged by another entity within a mythological or legendary context.
  • D. hasMythologicalFamily
    Indicates that an entity is related to another entity as part of its mythological family or lineage (e.g., gods, heroes, or legendary ancestors).
  • E. hasMythSource
    Indicates that something derives from, is based on, or is supported by a particular myth or mythological source.
  • 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_69c68a5f04188190ac266569c9280347 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f24c1c208190a3d11e816888760d completed March 27, 2026, 9:10 p.m.
PD Predicate disambiguation batch_69c6f0323b2c819098ab72c33e6d8534 completed March 27, 2026, 9:01 p.m.
Created at: March 27, 2026, 3:09 p.m.