Triple
T487066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appomattox Court House, Virginia |
E9900
|
entity |
| Predicate | preservationFocus |
P14039
|
FINISHED |
| Object | Civil War surrender site |
—
|
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: Civil War surrender site | Statement: [Appomattox Court House, Virginia, preservationFocus, Civil War surrender site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preservationFocus Context triple: [Appomattox Court House, Virginia, preservationFocus, Civil War surrender site]
-
A.
stateOfPreservation
Indicates the condition or degree to which something has been maintained, conserved, or kept intact over time.
-
B.
preservedAt
Indicates that something is kept, maintained, or conserved in a particular place or context.
-
C.
preservationPolicy
Indicates the rules or strategy governing how something is maintained, protected, and retained over time.
-
D.
heritageManagement
Indicates the management, preservation, and regulation of cultural or natural heritage resources by responsible entities.
-
E.
conservationValue
Indicates the degree to which something is considered important or valuable for conservation or protection of natural or cultural resources.
- F. None of above. chosen
Provenance (4 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0de66308190a18503a482881cfc |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf63fbc819090ea6ca11f39116a |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebb2c908190960a4d0c014304cd |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.