Triple
T782932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul W. Tibbets Jr. |
E16536
|
entity |
| Predicate | reasonForNoGrave |
P19571
|
FINISHED |
| Object | to avoid his grave becoming a site of protest or vandalism |
—
|
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 avoid his grave becoming a site of protest or vandalism | Statement: [Paul W. Tibbets Jr., reasonForNoGrave, to avoid his grave becoming a site of protest or vandalism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForNoGrave Context triple: [Paul W. Tibbets Jr., reasonForNoGrave, to avoid his grave becoming a site of protest or vandalism]
-
A.
notBuriedHere
Indicates that the entity in question is explicitly not buried at the specified location.
-
B.
burialPlace
Indicates the location where a person or entity is buried.
-
C.
locatedInCemetery
Indicates that one entity is situated within the grounds or area of a cemetery.
-
D.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
E.
hasNotableBurials
Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7686d0881908c2a4395059be02c |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50db97c8190a1c55673f4a357b4 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a67e69288190b3dc278c5bd94155 |
completed | March 1, 2026, 8:50 p.m. |
Created at: March 1, 2026, 7:37 p.m.