Triple
T20415139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pickett’s Division |
E500692
|
entity |
| Predicate | approximateDateOfGettysburgEngagement |
P61852
|
FINISHED |
| Object | July 3, 1863 |
—
|
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: July 3, 1863 | Statement: [Pickett’s Division, approximateDateOfGettysburgEngagement, July 3, 1863]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDateOfGettysburgEngagement Context triple: [Pickett’s Division, approximateDateOfGettysburgEngagement, July 3, 1863]
-
A.
GettysburgAddressDate
Indicates the specific date on which the Gettysburg Address was delivered.
-
B.
dayOfKeyGettysburgAction
chosen
Indicates the specific calendar day on which a key action or event related to the Battle of Gettysburg occurred.
-
C.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
D.
approximateTimeOfDayOfEventCommemorated
Indicates the general time of day during which the commemorated event is understood to have occurred.
-
E.
approximateInaugurationYear
Indicates the estimated or roughly known year in which an inauguration event took place.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a437eec8190a20c89a236dd5bc0 |
completed | April 20, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.