Triple
T31950360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marksville culture |
E815761
|
entity |
| Predicate | hasCeremonialism |
P129522
|
FINISHED |
| Object | mortuary ceremonialism |
—
|
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: mortuary ceremonialism | Statement: [Marksville culture, hasCeremonialism, mortuary ceremonialism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCeremonialism Context triple: [Marksville culture, hasCeremonialism, mortuary ceremonialism]
-
A.
isCeremonial
Indicates that something is associated with, intended for, or used in a formal ceremony or ritual rather than for ordinary or practical purposes.
-
B.
hasCeremonialFunctions
Indicates that an entity performs or is associated with formal, ritualistic, or ceremonial roles or activities.
-
C.
hasCeremonies
chosen
Indicates that an entity conducts, includes, or is associated with one or more formal ceremonies or ritual events.
-
D.
ceremonialUse
Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
-
E.
haveCeremonialHead
Indicates that one entity serves as the formal or symbolic head or leader of another entity, typically without holding full executive power.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 1, 2026, 12:07 a.m.