Triple

T36243247
Position Surface form Disambiguated ID Type / Status
Subject Murrah ibn Ka‘b E891583 entity
Predicate inGenealogyBetween P184798 FINISHED
Object Ka‘b ibn Lu’ayy and Kilab ibn Murrah 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: Ka‘b ibn Lu’ayy and Kilab ibn Murrah | Statement: [Murrah ibn Ka‘b, inGenealogyBetween, Ka‘b ibn Lu’ayy and Kilab ibn Murrah]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inGenealogyBetween
Context triple: [Murrah ibn Ka‘b, inGenealogyBetween, Ka‘b ibn Lu’ayy and Kilab ibn Murrah]
  • A. hasGenealogicalSignificance
    Indicates that something holds importance or relevance within a genealogical or family-lineage context.
  • B. hasGenealogicalInterest
    Indicates a relationship in which one entity has a research, documentation, or personal interest in the family history or lineage of another entity.
  • C. genealogicalFunction
    Indicates a genealogical relationship or role that one entity holds in relation to another within a family or ancestry structure.
  • D. hasGenealogicalRelation
    Indicates that there exists a family or ancestry-based relationship (such as parent, child, sibling, or more distant kinship) between the related entities.
  • E. hasGenealogy
    Indicates that one entity possesses or is associated with the genealogical record, lineage, or ancestry information of another entity.
  • F. None of above. chosen

Provenance (4 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_69f76e44993481908fa75e4c48d0aab3 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b5f89c5c8190825ed5d4317c540c completed May 3, 2026, 8:54 p.m.
PD Predicate disambiguation batch_69f7b4c44390819084fb5558b354658f completed May 3, 2026, 8:49 p.m.
PDg Predicate description generation batch_69f7b57aa0848190a22c31c3ff90e0ab completed May 3, 2026, 8:52 p.m.
Created at: May 3, 2026, 4:09 p.m.