Triple
T38434417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Bani Bishr |
E903900
|
entity |
| Predicate | tribalLineage |
P13151
|
FINISHED |
| Object | Qahtani Arabs |
—
|
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: Qahtani Arabs | Statement: [Al Bani Bishr, tribalLineage, Qahtani Arabs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribalLineage Context triple: [Al Bani Bishr, tribalLineage, Qahtani Arabs]
-
A.
hasTribalAncestor
Indicates that an entity is descended from, or has lineage tracing back to, a specified tribal ancestor.
-
B.
tribeOrGens
chosen
Indicates a relationship where an entity belongs to, is associated with, or is identified as a particular tribe or gens (clan/lineage group).
-
C.
ancestralGroup
Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
-
D.
tribeProgenitorOf
Indicates that one entity is the original ancestor or founding progenitor from which a particular tribe or tribal group descends.
-
E.
tribalAffiliationType
Indicates the specific type or category of tribal affiliation that characterizes the relationship between an entity and a tribe.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:31 p.m.