Triple
T28213953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey Veterans Memorial Cemetery |
E711253
|
entity |
| Predicate | burialEligibilityIncludes |
P47508
|
FINISHED |
| Object | U.S. military veterans |
—
|
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: U.S. military veterans | Statement: [New Jersey Veterans Memorial Cemetery, burialEligibilityIncludes, U.S. military veterans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialEligibilityIncludes Context triple: [New Jersey Veterans Memorial Cemetery, burialEligibilityIncludes, U.S. military veterans]
-
A.
hasBurialEligibility
chosen
Indicates that one entity is permitted or qualified to be buried in a particular place, context, or under specified conditions.
-
B.
burialStatus
Indicates the state or condition of whether and how an entity has been buried.
-
C.
deniedBurialBy
Indicates that one entity refused or withheld permission for another entity to be buried.
-
D.
burialHonors
Indicates a relationship where an entity is recognized or commemorated with special respect or distinction in the context of their burial or interment.
-
E.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6434bfb4881909c3309b3ec88c17a |
completed | May 2, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:41 p.m.