Triple
T28219634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Military Memorial Cemetery |
E711415
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national military cemetery |
C54545
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: national military cemetery Context triple: [Federal Military Memorial Cemetery, instanceOf, national military cemetery]
-
A.
United States Navy cemetery
A United States Navy cemetery is a burial ground established or designated by the U.S. Navy for interring Navy personnel and eligible individuals, often located at or near naval installations and maintained with military honors and traditions.
-
B.
national memorial site
A national memorial site is a designated place of remembrance established by a nation to honor significant historical events, individuals, or collective sacrifices central to its identity and heritage.
-
C.
United States National Memorial
A United States National Memorial is a federally designated site that commemorates a significant person, event, or idea in American history, often through monuments, preserved locations, or interpretive installations.
-
D.
Confederate cemetery
A Confederate cemetery is a burial ground dedicated to interring soldiers and individuals associated with the Confederate States of America, often marked by period-specific monuments and memorials.
-
E.
United States National Military Park
A United States National Military Park is a federally protected area that preserves and interprets significant military battlefields or related historic sites for public education, commemoration, and recreation.
- F. None of above. chosen
Provenance (1 batch)
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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 10:45 p.m.