Triple

T36775479
Position Surface form Disambiguated ID Type / Status
Subject Tig E908604 entity
Predicate comparativeMythologyEquivalent P126907 FINISHED
Object Týr 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: Týr | Statement: [Tig, comparativeMythologyEquivalent, Týr]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: comparativeMythologyEquivalent
Context triple: [Tig, comparativeMythologyEquivalent, Týr]
  • A. equivalentMythologicalName
    Indicates that two entities share the same identity in mythology, representing different names or versions of the same mythological figure.
  • B. equivalentInRomanMythology
    Indicates that one entity corresponds to or is identified as the Roman-mythology counterpart of another entity from a different mythological tradition.
  • C. equivalentInGreekReligion
    Indicates that two religious figures, concepts, or practices are counterparts or direct analogues of each other within the context of Greek religion.
  • D. comparableDeity chosen
    Indicates that one deity is considered comparable to another in terms of role, attributes, status, or function.
  • E. equivalentInAztecPantheon
    Indicates that one entity is considered the functional or symbolic counterpart of another within the Aztec pantheon.
  • 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_69f76e798aa08190ace31098d1b13e9f completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fd7b0503a08190ba07338365b6fcc9 completed May 8, 2026, 5:56 a.m.
PD Predicate disambiguation batch_69fd7a9733dc81909199f453c0cc2bc1 completed May 8, 2026, 5:54 a.m.
Created at: May 3, 2026, 4:12 p.m.