Triple

T36436792
Position Surface form Disambiguated ID Type / Status
Subject Jeturite tribe E897607 entity
Predicate biblicalGenealogyCategory P77019 FINISHED
Object Ishmaelite tribes 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: Ishmaelite tribes | Statement: [Jeturite tribe, biblicalGenealogyCategory, Ishmaelite tribes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: biblicalGenealogyCategory
Context triple: [Jeturite tribe, biblicalGenealogyCategory, Ishmaelite tribes]
  • A. genealogicalLine
    Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
  • B. covenantalLineage
    Indicates a relationship in which one entity belongs to, or is derived from, a line of individuals bound together by a formal or sacred covenant.
  • C. biblicalFigure
    Indicates that an entity is recognized as a person mentioned or characterized within the Bible.
  • D. genealogicalClassification chosen
    Indicates a relationship where one entity is categorized within a family or lineage structure relative to another, based on genealogical or ancestral connections.
  • E. chronologyWithinFamily
    Indicates that one family-related event or state occurs within the temporal span defined by another family-related event or state.
  • 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_69f76e56636481908eda808ab0273401 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7be9d07ac8190adf796cbef60daf6 completed May 3, 2026, 9:31 p.m.
PD Predicate disambiguation batch_69f7bcccd7988190aa5c931ff347d33c completed May 3, 2026, 9:23 p.m.
Created at: May 3, 2026, 4:10 p.m.