Triple
T23675888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Bliss |
E584871
|
entity |
| Predicate | wishedToBeBuriedFacing |
P152953
|
FINISHED |
| Object | Caribbean Sea |
—
|
NE NERFINISHED |
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: Caribbean Sea | Statement: [Baron Bliss, wishedToBeBuriedFacing, Caribbean Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wishedToBeBuriedFacing Context triple: [Baron Bliss, wishedToBeBuriedFacing, Caribbean Sea]
-
A.
buriedWith
Indicates that one entity is interred in the same grave, tomb, or burial site as another entity.
-
B.
isBuriedIn
Indicates that one entity is located beneath the ground or enclosed within another entity, typically as in a grave, tomb, or burial site.
-
C.
buriedFriend
Indicates that one entity has buried another entity with whom they have a friendship relationship.
-
D.
buriedNear
Indicates that one entity is interred or buried in close physical proximity to another entity.
-
E.
buriedAs
Indicates that one entity is interred or laid to rest in the manner, role, or context specified by another entity.
- F. None of above. chosen
Provenance (4 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f2e35c8190ada29694e2cbed37 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:51 p.m.