Triple
T11854566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barrah bint al-Harith |
E282000
|
entity |
| Predicate | dowryFromMuhammad |
P101873
|
FINISHED |
| Object | 400 dirhams |
—
|
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: 400 dirhams | Statement: [Barrah bint al-Harith, dowryFromMuhammad, 400 dirhams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dowryFromMuhammad Context triple: [Barrah bint al-Harith, dowryFromMuhammad, 400 dirhams]
-
A.
dowry
Indicates the transfer of wealth or property from a bride’s family to the groom or his family as part of a marriage arrangement.
-
B.
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.
-
C.
marriageToMuhammadArrangedBy
Indicates that an individual’s marriage to Muhammad was organized, negotiated, or set up by the specified arranger.
-
D.
marriageToMuhammadReason
Indicates the reason or motivation behind an individual's marriage to Muhammad.
-
E.
marriageToMuhammadOccasion
Indicates the specific occasion or event during which an individual entered into marriage with Muhammad.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a697f4108190af984932d2118472 |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.