Triple
T31257254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zayd ibn Harithah |
E797009
|
entity |
| Predicate | adoptedSonOf |
P152777
|
FINISHED |
| Object | Prophet Muhammad |
E4752
|
NE 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: Prophet Muhammad | Statement: [Zayd ibn Harithah, adoptedSonOf, Prophet Muhammad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedSonOf Context triple: [Zayd ibn Harithah, adoptedSonOf, Prophet Muhammad]
-
A.
hasAdoptiveSon
chosen
Indicates that one entity is the adoptive parent of another entity who is their son through legal adoption rather than biological descent.
-
B.
adoptedAs
Indicates that one entity has taken another into its family or care through a formal or recognized adoption process.
-
C.
listedAsSonOf
Indicates that one entity is recorded or designated as the son (male child) of another entity.
-
D.
adoptedSibling
Indicates that two individuals are siblings through adoption rather than by biological relation.
-
E.
saidToHaveBeenAdoptedBy
Indicates that one entity is reported or believed to have been adopted by another entity, without asserting it as an established fact.
- F. None of above.
Provenance (4 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_69f224dd5fdc81908a4cd24917b67668 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2a1e238ac881908baed2c6b1d9763a |
completed | June 11, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 9:12 p.m.