Triple
T25484816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abd Manaf ibn Qusay |
E638674
|
entity |
| Predicate | clanAncestorOf |
P369
|
FINISHED |
| Object | Banu Abd Shams |
—
|
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 Abd Shams | Statement: [Abd Manaf ibn Qusay, clanAncestorOf, Banu Abd Shams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanAncestorOf Context triple: [Abd Manaf ibn Qusay, clanAncestorOf, Banu Abd Shams]
-
A.
hasAncestralTo
Indicates that one entity is an ancestor of another, existing in an earlier generation within a lineage or heritage chain.
-
B.
hasAncestor
chosen
Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
-
C.
descendantClan
Indicates that one clan is a later-generation offshoot or subordinate lineage that originates from another clan.
-
D.
destinedAncestorOf
Indicates that one entity is fated or preordained to become an ancestor of another entity in the future.
-
E.
typeOfAncestor
Indicates that one entity is an ancestor (of any generational distance) of another entity.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f77ad3d0819080476fa776234cd0 |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:32 p.m.