Triple

T8598477
Position Surface form Disambiguated ID Type / Status
Subject Banu Zuhra E203611 entity
Predicate relatedTo P37 FINISHED
Object Banu Abd Shams E602176 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 Abd Shams | Statement: [Banu Zuhra, relatedTo, Banu Abd Shams]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Banu Abd Shams
Context triple: [Banu Zuhra, relatedTo, Banu Abd Shams]
  • A. Banu Abd Shams chosen
    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.
  • B. Banu Abd al-Dar
    Banu Abd al-Dar was a prominent clan of the Quraysh tribe in pre-Islamic and early Islamic Mecca, historically known for holding key custodial and ceremonial responsibilities related to the Kaaba.
  • C. Banu Ali
    Banu Ali is a lesser-known clan within the larger Banu Hashim lineage of the Quraysh tribe in early Islamic history.
  • D. 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.
  • E. Banu Ashar
    Banu Ashar was an Arab tribe of Yemen from which the early Islamic companion and governor Abu Musa al-Ashari descended.
  • 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_69ca832b56948190ba751cec255308f1 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cc46cc8b2081909c6aa45f8656f2ad completed March 31, 2026, 10:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf5140ec1c8190bbf37d4880191c03 completed April 3, 2026, 5:33 a.m.
Created at: March 30, 2026, 6:24 p.m.