Triple
T33904213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | necropolis of Vassieux-en-Vercors |
E869136
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French 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: French national military cemetery Context triple: [necropolis of Vassieux-en-Vercors, instanceOf, French national military cemetery]
-
A.
national military cemetery
chosen
A national military cemetery is a formally designated burial ground, maintained by a nation’s government, for honoring and interring its military personnel and often eligible veterans and their families.
-
B.
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.
-
C.
French military residential complex
A French military residential complex is a secured, purpose-built housing area that provides accommodation and essential communal facilities for members of the French armed forces and their families.
-
D.
Native American cemetery
A Native American cemetery is a sacred burial ground where Indigenous peoples inter their dead according to traditional cultural, spiritual, and community practices.
-
E.
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.
- F. None of above.
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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:48 a.m.