Triple
T33932027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | يزيد بن معاوية |
E869920
|
entity |
| Predicate | مكان الدفن المنسوب |
P118842
|
FINISHED |
| Object | دمشق أو نواحيها بحسب اختلاف الروايات |
—
|
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: دمشق أو نواحيها بحسب اختلاف الروايات | Statement: [يزيد بن معاوية, مكان الدفن المنسوب, دمشق أو نواحيها بحسب اختلاف الروايات]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: مكان الدفن المنسوب Context triple: [يزيد بن معاوية, مكان الدفن المنسوب, دمشق أو نواحيها بحسب اختلاف الروايات]
-
A.
tombLocatedIn
Indicates that a particular tomb is situated within or at a specified location or place.
-
B.
buriedNear
Indicates that one entity is interred or buried in close physical proximity to another entity.
-
C.
reputedBurialPlaceOf
chosen
Indicates a location that is widely believed or traditionally thought to be the burial place of a particular person or group.
-
D.
associatedTomb
Indicates a relationship in which an entity is linked to or connected with a particular tomb, such as by burial, ownership, dedication, or commemoration.
-
E.
مدفن_شہر
Indicates a relationship where a burial place (grave, tomb, or cemetery) is located in or associated with a particular city.
- 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.