Triple
T25619747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | المقوم بن عبد المطلب |
E642260
|
entity |
| Predicate | صلة_القرابة |
P7844
|
FINISHED |
| Object | عمّ النبي محمد |
—
|
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: عمّ النبي محمد | Statement: [المقوم بن عبد المطلب, صلة_القرابة, عمّ النبي محمد]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: صلة_القرابة Context triple: [المقوم بن عبد المطلب, صلة_القرابة, عمّ النبي محمد]
-
A.
hasFamilialTieTo
chosen
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
B.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
C.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
D.
politicalRelationship
Indicates a relationship in which entities are connected through political roles, alliances, affiliations, or interactions within a political context.
-
E.
closestLivingRelatives
Indicates that the related entities are the most closely related to each other among all currently living entities, in terms of evolutionary or genealogical proximity.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa1f5710819086f3ba4b42b6478b |
completed | May 2, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:03 p.m.