Triple
T33137543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdullah ibn Abi Umayya |
E848049
|
entity |
| Predicate | tribalAffiliationThroughFather |
P175094
|
FINISHED |
| Object | Banu Makhzum |
—
|
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: Banu Makhzum | Statement: [Abdullah ibn Abi Umayya, tribalAffiliationThroughFather, Banu Makhzum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribalAffiliationThroughFather Context triple: [Abdullah ibn Abi Umayya, tribalAffiliationThroughFather, Banu Makhzum]
-
A.
fatherClan
chosen
Indicates a kinship relationship where one entity belongs to, descends from, or is affiliated with the clan of the father of another entity.
-
B.
fatherEthnicity
Indicates the ethnic background or heritage associated specifically with a person's father.
-
C.
tribeProgenitorOf
Indicates that one entity is the original ancestor or founding progenitor from which a particular tribe or tribal group descends.
-
D.
hasPatrilinealOrigin
Indicates that something originates from or is derived through the male (father’s) ancestral line.
-
E.
originCountryOfPaternalLine
Indicates the country from which a person’s paternal family line (through the father’s side) originates.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:27 a.m.