Triple
T1343188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sawda bint Zamʿa |
E28510
|
entity |
| Predicate | chronologicalOrderAsWife |
P4764
|
FINISHED |
| Object | among the earliest wives after Khadija |
—
|
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: among the earliest wives after Khadija | Statement: [Sawda bint Zamʿa, chronologicalOrderAsWife, among the earliest wives after Khadija]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalOrderAsWife Context triple: [Sawda bint Zamʿa, chronologicalOrderAsWife, among the earliest wives after Khadija]
-
A.
firstWifeOf
Indicates that one person is the first woman to have been married to another person.
-
B.
spouseOrder
chosen
Indicates the position or sequence of a person among multiple spouses in a marital relationship.
-
C.
secondWifeOf
Indicates that one person is the second spouse (by order of marriage) of another person.
-
D.
firstHolderSpouseOf
Indicates that the first holder in the relation is the spouse (married partner) of the other holder.
-
E.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c2174d048190a6e9380df302265f |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.