Triple
T27453212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melquiades Estrada |
E692507
|
entity |
| Predicate | burialWish |
P162657
|
FINISHED |
| Object | to be buried in his hometown in Mexico |
—
|
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: to be buried in his hometown in Mexico | Statement: [Melquiades Estrada, burialWish, to be buried in his hometown in Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialWish Context triple: [Melquiades Estrada, burialWish, to be buried in his hometown in Mexico]
-
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.
burialText
Indicates that a text is inscribed on, associated with, or used in connection with a burial or funerary context.
-
D.
buriedFriend
Indicates that one entity has buried another entity with whom they have a friendship relationship.
-
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. 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_69ef5206c9248190b5975c2a7f9d229c |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62dc7c830819092e3f52733c8f60e |
completed | May 2, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62cd1912c8190ab3f3288442115a4 |
completed | May 2, 2026, 4:56 p.m. |
Created at: April 27, 2026, 12:48 p.m.