Triple
T9418689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anzick site |
E227092
|
entity |
| Predicate | burialTreatment |
P4043
|
FINISHED |
| Object | use of red ocher |
—
|
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: use of red ocher | Statement: [Anzick site, burialTreatment, use of red ocher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialTreatment Context triple: [Anzick site, burialTreatment, use of red ocher]
-
A.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
B.
burialPractice
chosen
Indicates the customary methods, rituals, or procedures a group uses to bury or inter their dead.
-
C.
usedForBurialOf
Indicates that something serves or is employed as a means, place, or object for burying a particular entity.
-
D.
burialContext
Indicates the circumstances or setting in which a burial takes place, such as associated practices, location, or cultural conditions surrounding the interment.
-
E.
burialPolicy
Indicates the rules or arrangements governing how and under what conditions a person’s body is to be buried.
- 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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd68cd1e3481909abcb715e2398120 |
completed | April 1, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:48 p.m.