Triple
T25410862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinana tribe |
E636690
|
entity |
| Predicate | notableDescendantClan |
P190323
|
FINISHED |
| Object | Banu Hashim |
—
|
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 Hashim | Statement: [Kinana tribe, notableDescendantClan, Banu Hashim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDescendantClan Context triple: [Kinana tribe, notableDescendantClan, Banu Hashim]
-
A.
notableClans
Indicates that there exists a significant or historically important clan associated with the subject.
-
B.
descendantClan
Indicates that one clan is a later-generation offshoot or subordinate lineage that originates from another clan.
-
C.
notableDescendantTribe
chosen
Indicates that a tribe has a particularly important or historically significant descendant tribe associated with it.
-
D.
notableClanOrigin
Indicates that an entity is notably associated with originating from, belonging to, or being historically linked to a particular clan.
-
E.
notableSurnameBranch
Indicates that a particular family branch is distinguished or noteworthy within a broader surname lineage.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 21, 2026, 1:53 p.m.