Triple

T29055264
Position Surface form Disambiguated ID Type / Status
Subject Musasir E735367 entity
Predicate hasTheonymicAssociation P2830 FINISHED
Object Haldi, chief god of Urartu 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: Haldi, chief god of Urartu | Statement: [Musasir, hasTheonymicAssociation, Haldi, chief god of Urartu]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTheonymicAssociation
Context triple: [Musasir, hasTheonymicAssociation, Haldi, chief god of Urartu]
  • A. hasEponymConnectionTo
    Indicates that one entity is named after, derived from, or otherwise linguistically or honorifically connected to another entity as its eponym.
  • B. hasToponymicAssociation
    Indicates a relationship where one entity is associated with, derived from, or named after a particular place or geographic name (toponym).
  • C. isAssociatedWith chosen
    Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
  • D. associatedWithEpithet
    Indicates that an entity is linked to or described by a particular epithet or descriptive label.
  • E. associatedName
    Indicates that one entity has an alternative or related name that is linked or connected to 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_69f077e64b88819094d37bdbca8191b3 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69f68a16debc8190a12f5f65ced055d7 completed May 2, 2026, 11:34 p.m.
PD Predicate disambiguation batch_69f6860def1c81909d79e1f088c4b5e5 completed May 2, 2026, 11:17 p.m.
Created at: April 28, 2026, 10:11 a.m.