Triple

T5673059
Position Surface form Disambiguated ID Type / Status
Subject Eye of Horus symbolism E125021 entity
Predicate hasMythologicalBasisIn P9595 FINISHED
Object myth of Horus and Seth 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: myth of Horus and Seth | Statement: [Eye of Horus symbolism, hasMythologicalBasisIn, myth of Horus and Seth]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMythologicalBasisIn
Context triple: [Eye of Horus symbolism, hasMythologicalBasisIn, myth of Horus and Seth]
  • A. hasMythologicalFeature
    Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
  • B. linkedToMythology chosen
    Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
  • C. mythologicalCategory
    Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
  • D. mythologicalEvent
    Indicates an event or occurrence that takes place within mythological narratives or traditions, often involving gods, heroes, or supernatural phenomena.
  • E. expandsMythologyOf
    Indicates that one entity broadens, enriches, or adds new elements to the mythological background or lore associated with another entity.
  • 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_69c008295c808190acfe78915e7d656a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c025303860819093e51f176babed71 completed March 22, 2026, 5:21 p.m.
PD Predicate disambiguation batch_69c021bc3894819084f37d14ba4b2644 completed March 22, 2026, 5:07 p.m.
Created at: March 22, 2026, 3:43 p.m.