Triple
T1343179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sawda bint Zamʿa |
E28510
|
entity |
| Predicate | timeWithMuhammad |
P27383
|
FINISHED |
| Object | lived with him in Medina |
—
|
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: lived with him in Medina | Statement: [Sawda bint Zamʿa, timeWithMuhammad, lived with him in Medina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeWithMuhammad Context triple: [Sawda bint Zamʿa, timeWithMuhammad, lived with him in Medina]
-
A.
associatedCaliph
Indicates a relationship where an entity is linked or connected to a specific caliph, typically through rule, patronage, affiliation, or historical association.
-
B.
positionInIslamicCalendar
Indicates the specific placement or ordering of a time point (such as a date or event) within the structure of the Islamic (Hijri) calendar.
-
C.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
D.
regardsAsOnlyProphetAfterMoses
Indicates that one entity considers another entity to be the sole legitimate prophet following Moses.
-
E.
timeInMyth
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
- 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_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. |
| PDg | Predicate description generation | batch_69a4c06721488190ac7f6e012f21af3d |
completed | March 1, 2026, 10:40 p.m. |
Created at: March 1, 2026, 7:56 p.m.