Triple
T10531117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pazyryk culture |
E248441
|
entity |
| Predicate | burialConstruction |
P68077
|
FINISHED |
| Object | timber chamber under mound |
—
|
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: timber chamber under mound | Statement: [Pazyryk culture, burialConstruction, timber chamber under mound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialConstruction Context triple: [Pazyryk culture, burialConstruction, timber chamber under mound]
-
A.
burialSiteFeature
chosen
Indicates a specific physical characteristic or element associated with a burial site, such as structures, markers, or other notable features present at the place of interment.
-
B.
burials
Indicates that one entity is interred or laid to rest in a grave or burial site associated with another entity.
-
C.
burialPractice
Indicates the customary methods, rituals, or procedures a group uses to bury or inter their dead.
-
D.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
E.
burialContext
Indicates the circumstances or setting in which a burial takes place, such as associated practices, location, or cultural conditions surrounding the interment.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a16915c8190ac4f3fd5e43c5fed |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:30 p.m.