Triple
T27904030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III Corps (Union Army) |
E705718
|
entity |
| Predicate | notableCommanderWoundedAtGettysburg |
P202079
|
FINISHED |
| Object | Daniel E. Sickles |
—
|
NE NERFINISHED |
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: Daniel E. Sickles | Statement: [III Corps (Union Army), notableCommanderWoundedAtGettysburg, Daniel E. Sickles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCommanderWoundedAtGettysburg Context triple: [III Corps (Union Army), notableCommanderWoundedAtGettysburg, Daniel E. Sickles]
-
A.
corpsCommanderAtGettysburg
Indicates that the subject served as a corps commander during the Battle of Gettysburg.
-
B.
commanderAtGettysburg
Indicates that the subject served as a military commander at the Battle of Gettysburg.
-
C.
armyCommanderAtGettysburg
Indicates that the person served as an army commander during the Battle of Gettysburg.
-
D.
brigadeCommanderAtGettysburg
Indicates that the subject served as a brigade commander during the Battle of Gettysburg.
-
E.
higherCommanderAtGettysburg
Indicates that one entity served as the superior military commander of another entity during the Battle of Gettysburg.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_6a004d0b46148190bcec4ea67acfe170 |
completed | May 10, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_6a004c92283081909f229c1720af155a |
completed | May 10, 2026, 9:14 a.m. |
| PDg | Predicate description generation | batch_6a004d0a95548190ac822cd1d54edf42 |
completed | May 10, 2026, 9:16 a.m. |
Created at: April 27, 2026, 6:44 p.m.