Triple
T30720701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Talladega |
E782147
|
entity |
| Predicate | notableCommanderForUnitedStates |
P17957
|
FINISHED |
| Object | Andrew Jackson |
E36939
|
NE 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: Andrew Jackson | Statement: [Battle of Talladega, notableCommanderForUnitedStates, Andrew Jackson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCommanderForUnitedStates Context triple: [Battle of Talladega, notableCommanderForUnitedStates, Andrew Jackson]
-
A.
notableCommanderAmerican
Indicates that the subject served as a notable military commander who is American.
-
B.
notableCommanderOf
chosen
Indicates that an individual is a distinguished or historically significant commander associated with leading a particular military unit, force, or organization.
-
C.
notableLeaderUS
Indicates that the subject is a prominent or historically significant leader associated with the United States.
-
D.
notableCommanderUnder
Indicates that one entity served as a notable military commander under the authority or leadership of another entity.
-
E.
notableUnionCommanderCommemorated
Indicates that a notable Union military commander is honored or memorialized in some way.
- F. None of above.
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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28b08663d881909f85dff60d7250cd |
completed | June 10, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:36 p.m.