Triple
T18679175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Bliss National Cemetery |
E456684
|
entity |
| Predicate | hasBurialBenefits |
P75212
|
FINISHED |
| Object | perpetual care |
—
|
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: perpetual care | Statement: [Fort Bliss National Cemetery, hasBurialBenefits, perpetual care]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBurialBenefits Context triple: [Fort Bliss National Cemetery, hasBurialBenefits, perpetual care]
-
A.
hasBurialEligibility
Indicates that one entity is permitted or qualified to be buried in a particular place, context, or under specified conditions.
-
B.
hasBenefit
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
C.
burialHonors
Indicates a relationship where an entity is recognized or commemorated with special respect or distinction in the context of their burial or interment.
-
D.
survivorBenefitMaximum
Indicates the maximum amount of benefits that can be paid to a survivor under a given policy, program, or arrangement.
-
E.
hasBenefitType
chosen
Indicates that an entity is associated with a specific category or type of benefit it provides or receives.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2783648190bb602e2b07eedf92 |
completed | April 19, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.