Triple

T10705460
Position Surface form Disambiguated ID Type / Status
Subject Fihr ibn Malik E252390 entity
Predicate ancestorOf P369 FINISHED
Object Banu Taym E148301 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: Banu Taym | Statement: [Fihr ibn Malik, ancestorOf, Banu Taym]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Banu Taym
Context triple: [Fihr ibn Malik, ancestorOf, Banu Taym]
  • A. Banu Taym chosen
    Banu Taym was a prominent clan of the Quraysh tribe in Mecca, historically notable as the clan of the first caliph, Abu Bakr.
  • B. Banu Nawfal
    Banu Nawfal was a prominent clan within the Quraysh tribe of Mecca, known for its role in pre-Islamic and early Islamic Arabian society.
  • C. Banu Jusham
    Banu Jusham was an Arab subtribe historically associated with the larger Banu Hilal tribal confederation, known from the early Islamic and medieval periods.
  • D. Banu Riyah
    Banu Riyah was an Arab tribal group that formed part of the larger Banu Hilal confederation, known for its role in the medieval Arab migrations into North Africa.
  • E. Banu Ta’i
    Banu Ta’i is an Arab tribe historically associated with the Tayy lineage, known for its early prominence in pre-Islamic and Islamic Arabia.
  • 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_69d6aa5cbabc8190973e683950d89faf completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6fddeb060819094cd125a68070eb2 completed April 9, 2026, 1:16 a.m.
NED1 Entity disambiguation (via context triple) batch_69dbd9cef8a48190a0ec4a27d5702e73 completed April 12, 2026, 5:43 p.m.
Created at: April 8, 2026, 9:12 p.m.