Triple
T20017244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monacan people |
E494753
|
entity |
| Predicate | traditionalBurialPractice |
P4043
|
FINISHED |
| Object | earthen burial mounds |
—
|
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: earthen burial mounds | Statement: [Monacan people, traditionalBurialPractice, earthen burial mounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalBurialPractice Context triple: [Monacan people, traditionalBurialPractice, earthen burial mounds]
-
A.
burialPractice
chosen
Indicates the customary methods, rituals, or procedures a group uses to bury or inter their dead.
-
B.
primaryDenominationOfBurials
Indicates the main religious denomination associated with the majority of burials at a given burial site or cemetery.
-
C.
burialPolicy
Indicates the rules or arrangements governing how and under what conditions a person’s body is to be buried.
-
D.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
E.
hasBurialCustoms
Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623d76808190988990a8dc263ef7 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.