Triple
T28732373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spotsylvania Court House National Cemetery |
E730695
|
entity |
| Predicate | burialsMostlyFromSide |
P45931
|
FINISHED |
| Object | Union Army |
—
|
NE NERFINISHED |
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: Union Army | Statement: [Spotsylvania Court House National Cemetery, burialsMostlyFromSide, Union Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialsMostlyFromSide Context triple: [Spotsylvania Court House National Cemetery, burialsMostlyFromSide, Union Army]
-
A.
burialDetail
Indicates details about how, where, and under what circumstances an entity is buried.
-
B.
buriedNear
Indicates that one entity is interred or buried in close physical proximity to another entity.
-
C.
hasBurialsFrom
chosen
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
D.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
E.
burials
Indicates that one entity is interred or laid to rest in a grave or burial site associated with 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 5:59 a.m.