Triple
T12347414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Culpeper National Cemetery |
E294391
|
entity |
| Predicate | hasTypeOfBurialGround |
P2743
|
FINISHED |
| Object | national military burial ground |
—
|
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: national military burial ground | Statement: [Culpeper National Cemetery, hasTypeOfBurialGround, national military burial ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfBurialGround Context triple: [Culpeper National Cemetery, hasTypeOfBurialGround, national military burial ground]
-
A.
hasTypeOfBurial
Indicates the specific kind or method of burial associated with an entity.
-
B.
hasTypeOfGrave
Indicates that an entity is associated with a specific kind or category of grave.
-
C.
hasCemeteryType
chosen
Indicates that a cemetery is classified as belonging to a specific type or category of cemetery.
-
D.
hasBurialVault
Indicates that an entity possesses or is associated with a specific burial vault used for interment or storage of remains.
-
E.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f7ba17481908b03af7316b28d9b |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.