Triple
T25606441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umm al-Fadl |
E641925
|
entity |
| Predicate | connectedToHouseholdOf |
P86281
|
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: [Umm al-Fadl, connectedToHouseholdOf, Prophet Muhammad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToHouseholdOf Context triple: [Umm al-Fadl, connectedToHouseholdOf, Prophet Muhammad]
-
A.
bondedToHouse
Indicates a relationship where an entity is legally or contractually obligated, tied, or pledged in connection to a specific house.
-
B.
sharesHouseholdWith
Indicates that two entities live together in the same household as co-residents.
-
C.
hasHouseholdMember
chosen
Indicates that one entity is a member of the same household as another entity.
-
D.
associatedHouse
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
-
E.
supportsHouseholdLinking
Indicates that one entity enables or facilitates the creation or maintenance of an association between multiple household entities.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 21, 2026, 4:38 p.m.