Triple

T7347535
Position Surface form Disambiguated ID Type / Status
Subject Fihr E169416 entity
Predicate descendant P5206 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, descendant, Banu Taym]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Banu Taym
Context triple: [Fihr, descendant, 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 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.
  • D. Banu Ali
    Banu Ali is a lesser-known clan within the larger Banu Hashim lineage of the Quraysh tribe in early Islamic history.
  • E. Banu Abd Shams
    Banu Abd Shams was a prominent clan of the Quraysh tribe in pre-Islamic and early Islamic Mecca, known for its influential leaders and political power.
  • 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_69c68a5878888190968ce4d04db8d69f completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f0f14f308190a9e5cb76c7790e49 completed March 27, 2026, 9:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69c83433ca8081909ab00d1fe3ab1041 completed March 28, 2026, 8:04 p.m.
Created at: March 27, 2026, 3:05 p.m.