Triple
T8844026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Appomattox Station |
E210457
|
entity |
| Predicate | LeeSurrenderDate |
P4667
|
FINISHED |
| Object | 1865-04-09 |
—
|
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: 1865-04-09 | Statement: [Battle of Appomattox Station, LeeSurrenderDate, 1865-04-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LeeSurrenderDate Context triple: [Battle of Appomattox Station, LeeSurrenderDate, 1865-04-09]
-
A.
surrenderDate
chosen
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
B.
surrenderYear
Indicates the year in which an entity formally surrendered, ending its resistance or hostilities.
-
C.
surrenderedAfter
Indicates that one entity surrendered following or as a consequence of another specified event, action, or time.
-
D.
yearOfSurrender
Indicates the specific calendar year in which an entity formally surrendered or yielded, typically ending its resistance or control.
-
E.
garrisonSurrenderedTo
Indicates that a defending military garrison formally capitulated and yielded control to another party.
- 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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc608a73c88190875409fef79ffc8a |
completed | April 1, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:48 p.m.