Triple
T28732393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spotsylvania Court House National Cemetery |
E730695
|
entity |
| Predicate | timePeriodOfPrimaryBurials |
P68383
|
FINISHED |
| Object | 1860s |
—
|
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: 1860s | Statement: [Spotsylvania Court House National Cemetery, timePeriodOfPrimaryBurials, 1860s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfPrimaryBurials Context triple: [Spotsylvania Court House National Cemetery, timePeriodOfPrimaryBurials, 1860s]
-
A.
timePeriodOfBurials
chosen
Indicates the span of time during which the burials associated with an entity took place.
-
B.
mainBurialsPeriodStart
Indicates the time period or date when the primary or main phase of burials at a site or within a context began.
-
C.
periodOfBurial
Indicates the time period or date range during which the burial of an entity took place.
-
D.
mainBurialsPeriodEnd
Indicates the time period or date when the primary phase of burials at a site or context came to an end.
-
E.
earliestBurials
Indicates that the referenced burials are among the first or oldest known interments associated with a given site, group, or context.
- 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_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 5:59 a.m.