Triple
T33261300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alakul culture |
E851519
|
entity |
| Predicate | hasBurialOrientation |
P74935
|
FINISHED |
| Object | often west–east |
—
|
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: often west–east | Statement: [Alakul culture, hasBurialOrientation, often west–east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBurialOrientation Context triple: [Alakul culture, hasBurialOrientation, often west–east]
-
A.
hasTypeOfBurial
Indicates the specific kind or method of burial associated with an entity.
-
B.
wishedToBeBuriedFacing
Indicates that a person expressed a desire to be buried with their body oriented toward a specific direction or location.
-
C.
hasBurialCustoms
chosen
Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
-
D.
hasBurialGoodType
Indicates that a burial includes or is associated with a specific type or category of burial good.
-
E.
hasBurialMonumentType
Indicates that an entity is associated with a burial whose monument is of a specified type.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:31 a.m.