Triple
T28761930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Heth |
E726137
|
entity |
| Predicate | actionAtGettysburg |
P165559
|
FINISHED |
| Object | ordered advance toward Gettysburg on July 1, 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: ordered advance toward Gettysburg on July 1, 1863 | Statement: [Henry Heth, actionAtGettysburg, ordered advance toward Gettysburg on July 1, 1863]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actionAtGettysburg Context triple: [Henry Heth, actionAtGettysburg, ordered advance toward Gettysburg on July 1, 1863]
-
A.
commanderAtGettysburg
Indicates that the subject served as a military commander at the Battle of Gettysburg.
-
B.
opposingForceAtGettysburg
Indicates that one entity served as the opposing military force to another during the Battle of Gettysburg.
-
C.
commandedByDuringGettysburg
Indicates that one entity served as the commanding authority over another entity specifically during the Battle of Gettysburg.
-
D.
sideAtGettysburg
Indicates that an entity participated as a member of a particular side (e.g., Union or Confederate) in the Battle of Gettysburg.
-
E.
GettysburgAddressDate
Indicates the specific date on which the Gettysburg Address was delivered.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:12 a.m.