Triple
T1378869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaynab bint Jahsh |
E29289
|
entity |
| Predicate | householdPractice |
P27135
|
FINISHED |
| Object | gave much of her income in charity |
—
|
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: gave much of her income in charity | Statement: [Zaynab bint Jahsh, householdPractice, gave much of her income in charity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: householdPractice Context triple: [Zaynab bint Jahsh, householdPractice, gave much of her income in charity]
-
A.
household
Indicates that two or more entities belong to or are part of the same household unit, typically sharing a residence and domestic life.
-
B.
homePractice
Indicates that an activity, skill, or task is being practiced or carried out in a home setting rather than in a formal or external environment.
-
C.
house1
Indicates that something is identified or classified as a house or dwelling.
-
D.
typicalPractice
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
-
E.
house2
Indicates a relationship where one entity is a secondary, related, or alternative house associated with another entity.
- F. None of above. chosen
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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c3187f248190a5813274b0ef944d |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befcabdc8190a9f05d002603f81c |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c0335f7081908d50046ced4cdee0 |
completed | March 1, 2026, 10:39 p.m. |
Created at: March 1, 2026, 7:59 p.m.