Triple
T14110473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keita dynasty |
E339620
|
entity |
| Predicate | ancestralClaim |
P30356
|
FINISHED |
| Object | descent from Bilal ibn Rabah |
—
|
LITERAL 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: descent from Bilal ibn Rabah | Statement: [Keita dynasty, ancestralClaim, descent from Bilal ibn Rabah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancestralClaim Context triple: [Keita dynasty, ancestralClaim, descent from Bilal ibn Rabah]
-
A.
heritageClaimedBy
Indicates that a particular heritage, tradition, or cultural legacy is asserted or identified as belonging to a specific entity.
-
B.
lineageClaim
Indicates a claim or assertion that one entity is descended from, or belongs to the ancestral line of, another entity.
-
C.
dynasticClaim
Indicates a relationship where one party asserts a hereditary or lineage-based right to rule, inherit, or hold authority over another.
-
D.
ancestralStatus
Indicates that one entity holds a particular ancestral or lineage-based relationship or status in relation to another entity.
-
E.
claimedDescentFrom
chosen
Indicates that one entity asserts or maintains that it is descended from, or originates genealogically from, 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600e6a688190a1243a30ae9b7157 |
completed | April 14, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.