Triple
T9253107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etowah Indian Mounds |
E222373
|
entity |
| Predicate | containsBurials |
P62966
|
FINISHED |
| Object | elite burials |
—
|
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: elite burials | Statement: [Etowah Indian Mounds, containsBurials, elite burials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsBurials Context triple: [Etowah Indian Mounds, containsBurials, elite burials]
-
A.
hasBurialsOf
chosen
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
B.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
C.
hasNotableBurials
Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
-
D.
containsHeartBurial
Indicates that one entity includes or features the burial of a heart within it.
-
E.
burials
Indicates that one entity is interred or laid to rest in a grave or burial site associated with another entity.
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd06b0789481908e8e44ebf1b3c713 |
completed | April 1, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:31 p.m.