Triple
T32348518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alawi dynasty |
E826530
|
entity |
| Predicate | hasAncestralClaimTo |
P149753
|
FINISHED |
| Object | Prophet Muhammad |
—
|
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: Prophet Muhammad | Statement: [Alawi dynasty, hasAncestralClaimTo, Prophet Muhammad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralClaimTo Context triple: [Alawi dynasty, hasAncestralClaimTo, Prophet Muhammad]
-
A.
hasTribalAncestor
Indicates that an entity is descended from, or has lineage tracing back to, a specified tribal ancestor.
-
B.
alsoHasAncestry
Indicates that an entity possesses an additional ancestral lineage or heritage beyond its primary recorded ancestry.
-
C.
allegedAncestor
chosen
Indicates that one entity is claimed or suspected to be an ancestor of another, without confirming that the ancestral relationship is true.
-
D.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
E.
hasAncestralLand
Indicates that an entity possesses land inherited from its ancestors or traditionally associated with its 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 1, 2026, 12:49 a.m.