Triple

T20344040
Position Surface form Disambiguated ID Type / Status
Subject Shimea E495817 entity
Predicate nameVariant P744 FINISHED
Object Shimeah 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: Shimeah | Statement: [Shimea, nameVariant, Shimeah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shimeah
Context triple: [Shimea, nameVariant, Shimeah]
  • A. Shimeah chosen
    Shimeah is a biblical figure mentioned in the Hebrew Bible, known primarily as an alternative name for Shammah.
  • B. Shemaiah
    Shemaiah is a biblical figure known primarily as the father of Uriah mentioned in the Hebrew Bible.
  • C. Seraiah
    Seraiah is a biblical figure mentioned in the Hebrew Bible, known as a priestly ancestor in the lineage leading to Jehozadak.
  • D. Huelel
    Huelel is the self-designated name (endonym) used by the Esselen people, an Indigenous group native to the central coast of California.
  • E. Abijam of Judah
    Abijam of Judah was a king of the ancient Kingdom of Judah, known from the Hebrew Bible for his brief and troubled reign marked by continued idolatry and warfare with the northern Kingdom of Israel.
  • 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_69e0b4a3320881909495ae8bc30bc2dc completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67837bef8819091e552d1c8a1665c completed April 20, 2026, 7:02 p.m.
Created at: April 16, 2026, 11:24 a.m.