Triple
T6847796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. National Cemetery |
E157939
|
entity |
| Predicate | burialCostsForEligible |
P22931
|
FINISHED |
| Object | no cost for gravesite |
—
|
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: no cost for gravesite | Statement: [U.S. National Cemetery, burialCostsForEligible, no cost for gravesite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialCostsForEligible Context triple: [U.S. National Cemetery, burialCostsForEligible, no cost for gravesite]
-
A.
burialHonors
Indicates a relationship where an entity is recognized or commemorated with special respect or distinction in the context of their burial or interment.
-
B.
burialStatus
Indicates the state or condition of whether and how an entity has been buried.
-
C.
burialPolicy
chosen
Indicates the rules or arrangements governing how and under what conditions a person’s body is to be buried.
-
D.
hasBurialEligibility
Indicates that one entity is permitted or qualified to be buried in a particular place, context, or under specified conditions.
-
E.
containsHeartBurial
Indicates that one entity includes or features the burial of a heart within it.
- 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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d7ce3e7481908e0472b8faafa473 |
completed | March 27, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:20 p.m.