Triple
T35233784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asad ibn Hāshim |
E1017313
|
entity |
| Predicate | kinshipToMuḥammad |
P120349
|
FINISHED |
| Object | paternal great-uncle |
—
|
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: paternal great-uncle | Statement: [Asad ibn Hāshim, kinshipToMuḥammad, paternal great-uncle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kinshipToMuḥammad Context triple: [Asad ibn Hāshim, kinshipToMuḥammad, paternal great-uncle]
-
A.
associatedPersonRelationToMuhammad
chosen
Indicates the specific type of relationship or connection a person has to Muhammad.
-
B.
caliphalFamilyMember
Indicates that one entity is a member of a caliphal family, i.e., related by blood or lineage to a caliph or ruling caliphal dynasty.
-
C.
relationshipToMuhajirun
Indicates the nature or type of relationship an entity has with the Muhajirun (the early Muslim emigrants from Mecca).
-
D.
familyRelationInIslamicTradition
Indicates a familial relationship as defined within Islamic tradition, including kinship ties, marital bonds, and lineage-based connections governed by Islamic law and customs.
-
E.
relationToUthman
Indicates the type of relationship or connection an entity has to Uthman.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.