Triple
T1441888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maymunah bint al-Harith |
E31091
|
entity |
| Predicate | burialPlace |
P196
|
FINISHED |
| Object | Sarif |
E165343
|
NE 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: Sarif | Statement: [Maymunah bint al-Harith, burialPlace, Sarif]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sarif Context triple: [Maymunah bint al-Harith, burialPlace, Sarif]
-
A.
Sarif
chosen
Sarif is a locality near Mecca in present-day Saudi Arabia, historically noted as the site of Maymunah bint al-Harith’s marriage to the Prophet Muhammad.
-
B.
Sifra
Sifra is a classical rabbinic midrash on the Book of Leviticus that systematically expounds its legal (halakhic) passages.
-
C.
Shifnal
Shifnal is a small market town in Shropshire, England, known for its historic buildings and proximity to Telford.
-
D.
SIF
SIF is the governing body for ice hockey in Sweden, overseeing the national teams and domestic competitions.
-
E.
Schalk
Schalk is a masculine given name of Afrikaans and Dutch origin, commonly used in South Africa.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5320728819095d9ed2439fa7d31 |
completed | March 1, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad0e6e12748190baeb91ba843a716f |
completed | March 8, 2026, 5:51 a.m. |
Created at: March 1, 2026, 8 p.m.