Triple
T19159158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Pedro de Atacama culture |
E469004
|
entity |
| Predicate | hasBurialGoods |
P46542
|
FINISHED |
| Object | ceramic vessels |
—
|
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: ceramic vessels | Statement: [San Pedro de Atacama culture, hasBurialGoods, ceramic vessels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBurialGoods Context triple: [San Pedro de Atacama culture, hasBurialGoods, ceramic vessels]
-
A.
hasBurialCustoms
Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
-
B.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
C.
hasGraveGoods
chosen
Indicates that a burial or grave contains associated objects or goods placed with the deceased.
-
D.
hasBurialVault
Indicates that an entity possesses or is associated with a specific burial vault used for interment or storage of remains.
-
E.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eebb573081909fcd6af8aff8692b |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.