Triple
T3882883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neptune, Pacific Ocean (cremated remains scattered) |
E92865
|
entity |
| Predicate | intermentType |
P6490
|
FINISHED |
| Object | cremated remains scattered at sea |
—
|
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: cremated remains scattered at sea | Statement: [Neptune, Pacific Ocean (cremated remains scattered), intermentType, cremated remains scattered at sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intermentType Context triple: [Neptune, Pacific Ocean (cremated remains scattered), intermentType, cremated remains scattered at sea]
-
A.
cemeteryType
Indicates the specific kind or classification of a cemetery associated with an entity.
-
B.
hasTypeOfBurial
chosen
Indicates the specific kind or method of burial associated with an entity.
-
C.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
D.
burialStatus
Indicates the state or condition of whether and how an entity has been buried.
-
E.
containsHeartBurial
Indicates that one entity includes or features the burial of a heart within it.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeec8e8b3481909617ca0e37f8a6d4 |
completed | March 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.