Triple
T21265199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subeshi cemetery |
E524106
|
entity |
| Predicate | burialOrientation |
P121622
|
FINISHED |
| Object | generally east–west |
—
|
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: generally east–west | Statement: [Subeshi cemetery, burialOrientation, generally east–west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialOrientation Context triple: [Subeshi cemetery, burialOrientation, generally east–west]
-
A.
burialPractice
Indicates the customary methods, rituals, or procedures a group uses to bury or inter their dead.
-
B.
burialDetail
chosen
Indicates details about how, where, and under what circumstances an entity is buried.
-
C.
burialStatus
Indicates the state or condition of whether and how an entity has been buried.
-
D.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
E.
burialCoordinates
Indicates the geographic location where an entity is buried, typically expressed as spatial coordinates.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735ebe09081909f74301e91b4d3d7 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 16, 2026, 4 p.m.