Triple

T15853506
Position Surface form Disambiguated ID Type / Status
Subject Shem E384397 entity
Predicate ancestorOf P369 FINISHED
Object Eber E801811 NE 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: Eber | Statement: [Shem, ancestorOf, Eber]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eber
Context triple: [Shem, ancestorOf, Eber]
  • A. Eber chosen
    Eber is a biblical patriarch regarded as an ancestor of the Hebrews, from whom the term “Hebrew” is traditionally derived.
  • B. Eber-Nari
    Eber-Nari was an ancient Near Eastern region of the Achaemenid Persian Empire, roughly corresponding to the Levant and parts of Syria and Mesopotamia.
  • C. Togodumnus
    Togodumnus was a 1st-century AD British tribal leader, likely a king of the Catuvellauni, who opposed the Roman invasion of Britain under Emperor Claudius.
  • D. Eraric
    Eraric was a short-reigned Ostrogothic king in Italy during the mid-6th century, known primarily for his brief and unstable rule before being succeeded by Totila.
  • E. Erekle II
    Erekle II was an 18th-century Georgian king of Kartli and Kakheti known for his military leadership, internal reforms, and efforts to preserve Georgian independence amid Persian and Russian influence.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d86da422088190aac39e32e6c68429 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e14cae96648190884a85f68b6e9fe1 completed April 16, 2026, 8:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffa14977408190815ef02cc54075cc completed May 9, 2026, 9:04 p.m.
Created at: April 10, 2026, 4:50 a.m.