Triple

T18694226
Position Surface form Disambiguated ID Type / Status
Subject Epaphus E457073 entity
Predicate descendant P5206 FINISHED
Object Belus 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: Belus | Statement: [Epaphus, descendant, Belus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Belus
Context triple: [Epaphus, descendant, Belus]
  • A. Belus chosen
    Belus is a figure in Greek mythology, often portrayed as a king of Egypt or Libya and an ancestor of several notable mythic lineages.
  • B. Veles
    Veles is a city in central North Macedonia known as an important industrial and transportation hub situated along the Vardar River.
  • C. Theus
    Theus is the surname of Reggie Theus, a former American professional basketball player and coach known for his NBA career and later coaching roles.
  • D. Svetovid
    Svetovid is a major Slavic deity, often depicted with four heads and associated with war, abundance, and prophecy.
  • E. Lugus
    Lugus is a Celtic god associated with light, craftsmanship, and commerce, often identified with the Roman Mercury and widely venerated across ancient Gaul and Iberia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d391eb488190ac2e9abf5bf255e4 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e562e66a188190801fd95f9be26042 completed April 19, 2026, 11:19 p.m.
Created at: April 10, 2026, 11:49 a.m.