Triple
T34183390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | عثمان بن عفان |
E876887
|
entity |
| Predicate | دُفن_في |
P58438
|
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: [عثمان بن عفان, دُفن_في, البقيع (المدينة المنورة)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: دُفن_في Context triple: [عثمان بن عفان, دُفن_في, البقيع (المدينة المنورة)]
-
A.
isBuriedIn
chosen
Indicates that one entity is located beneath the ground or enclosed within another entity, typically as in a grave, tomb, or burial site.
-
B.
foundInTomb
Indicates that an object or entity was discovered within a specific tomb or burial site.
-
C.
buriedWith
Indicates that one entity is interred in the same grave, tomb, or burial site as another entity.
-
D.
buriedUnder
Indicates that one entity is located beneath another entity in such a way that it is covered or concealed by it, as if buried.
-
E.
tombLocatedIn
Indicates that a particular tomb is situated within or at a specified location or place.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710075ce48190ad41ebd08e640c1e |
completed | May 3, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.