Triple
T5910059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Oud Cemetery |
E131435
|
entity |
| Predicate | cityCemeteryRole |
P38888
|
FINISHED |
| Object | major cemetery serving Riyadh |
—
|
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: major cemetery serving Riyadh | Statement: [Al Oud Cemetery, cityCemeteryRole, major cemetery serving Riyadh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityCemeteryRole Context triple: [Al Oud Cemetery, cityCemeteryRole, major cemetery serving Riyadh]
-
A.
necropolisRole
Indicates that an entity has a specific functional or social role in relation to a necropolis (a large cemetery or burial ground).
-
B.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
C.
isCemeteryFor
chosen
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
D.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with another entity.
-
E.
cemeteryArea
Indicates that an area or region is designated, used, or recognized as a cemetery.
- 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0334fcf6481908e8e74105de9d49b |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:59 p.m.