Triple
T5840444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tune ship |
E129578
|
entity |
| Predicate | burialContained |
P65830
|
FINISHED |
| Object | human remains |
—
|
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: human remains | Statement: [Tune ship, burialContained, human remains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialContained Context triple: [Tune ship, burialContained, human remains]
-
A.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
B.
buriedWith
Indicates that one entity is interred in the same grave, tomb, or burial site as another entity.
-
C.
possiblyBurialOf
chosen
Indicates that one entity is a potential or uncertain burial site, grave, or interment location associated with another entity.
-
D.
burialText
Indicates that a text is inscribed on, associated with, or used in connection with a burial or funerary context.
-
E.
isBuriedIn
Indicates that one entity is located beneath the ground or enclosed within another entity, typically as in a grave, tomb, or burial site.
- 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_69c0084bd31c8190a796bb6284845e83 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.