Triple

T13850191
Position Surface form Disambiguated ID Type / Status
Subject Bethuel E332915 entity
Predicate livesIn P40 FINISHED
Object Aram-naharaim E1054845 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: Aram-naharaim | Statement: [Bethuel, livesIn, Aram-naharaim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aram-naharaim
Context triple: [Bethuel, livesIn, Aram-naharaim]
  • A. Aram-naharaim chosen
    Aram-naharaim is an ancient region in northern Mesopotamia, often identified with the area between the Tigris and Euphrates rivers and frequently mentioned in the Hebrew Bible.
  • B. Aram
    Aram is the first book of the ancient Tamil text Tirukkural, focusing on virtue, ethics, and righteous living.
  • C. Aram
    Aram is a common Armenian given name with deep historical and cultural significance in Armenian heritage.
  • D. Shammua
    Shammua is a biblical figure mentioned in the Old Testament, known primarily as one of the sons of David.
  • E. Abel Beth Maacah
    Abel Beth Maacah was an ancient fortified city in northern Israel, mentioned in the Hebrew Bible as a strategic site near the borders of Aram and Phoenicia.
  • 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_69d81c5ba13c8190839315f54768acfd completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de02d8fb788190baef7537be2baecb completed April 14, 2026, 9:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c0f35ba48190b8b071679251233f completed May 3, 2026, 9:41 p.m.
Created at: April 9, 2026, 10:14 p.m.