Triple
T27883872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancestors of Muhammad |
E705169
|
entity |
| Predicate | hasNotableSublineage |
P104422
|
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: [Ancestors of Muhammad, hasNotableSublineage, Banu Hashim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSublineage Context triple: [Ancestors of Muhammad, hasNotableSublineage, Banu Hashim]
-
A.
hasNotableLineage
Indicates that an entity descends from, or is associated with, a distinguished or historically significant family, ancestry, or heritage.
-
B.
hasNotableLineageFor
Indicates that one entity possesses a distinguished or noteworthy ancestry, heritage, or lineage in relation to another entity.
-
C.
hasNotableSubtribe
chosen
Indicates that an entity (typically a larger tribal or ethnic group) includes a particular subtribe that is especially recognized or notable.
-
D.
hasPatrilinealOrigin
Indicates that something originates from or is derived through the male (father’s) ancestral line.
-
E.
hasTribalAncestor
Indicates that an entity is descended from, or has lineage tracing back to, a specified tribal ancestor.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: April 27, 2026, 6:31 p.m.