Triple
T7229391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu Lahab |
E154864
|
entity |
| Predicate | relationshipToMuhammad |
P74796
|
FINISHED |
| Object | paternal 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 uncle | Statement: [Abu Lahab, relationshipToMuhammad, paternal uncle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToMuhammad Context triple: [Abu Lahab, relationshipToMuhammad, paternal uncle]
-
A.
relationToIslam
Indicates how an entity is connected or related to Islam, such as through belief, practice, affiliation, or influence.
-
B.
relationToKhalidIbnAlWalid
Indicates a relationship or association that an entity has with Khalid ibn al-Walid.
-
C.
صلة_بالنبي_محمد
chosen
Indicates a relationship of connection, association, or kinship with the Prophet Muhammad.
-
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.
marriageToMuhammadType
Indicates a marital relationship in which the person is (or was) married to Muhammad, specifying that the marriage is to the individual identified as Muhammad.
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea0d9b6c8190a0b5f0ab8d5cca19 |
completed | March 27, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.