Triple
T30355082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | حجرة عائشة |
E772120
|
entity |
| Predicate | wasBurialPlaceOf |
P196
|
FINISHED |
| Object | النبي محمد |
—
|
NE NERFINISHED |
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: [حجرة عائشة, wasBurialPlaceOf, النبي محمد]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasBurialPlaceOf Context triple: [حجرة عائشة, wasBurialPlaceOf, النبي محمد]
-
A.
burialPlace
chosen
Indicates the location where a person or entity is buried.
-
B.
reputedBurialPlaceOf
Indicates a location that is widely believed or traditionally thought to be the burial place of a particular person or group.
-
C.
locatedInTheAdministrativeTerritorialEntityOfBurial
Indicates that the place or site referenced is situated within the specified administrative territorial entity where the burial is located.
-
D.
isBuriedIn
Indicates that one entity is located beneath the ground or enclosed within another entity, typically as in a grave, tomb, or burial site.
-
E.
hasPartInGrave
Indicates that an entity includes another entity as a physical component or element within a grave.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6823e27d88190af8342b01f9876e8 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:56 p.m.