Triple
T27492781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Burgwyn Anderson |
E693935
|
entity |
| Predicate | promotionToBrigadierGeneralDate |
P43971
|
FINISHED |
| Object | 1862-06-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: 1862-06-09 | Statement: [George Burgwyn Anderson, promotionToBrigadierGeneralDate, 1862-06-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionToBrigadierGeneralDate Context triple: [George Burgwyn Anderson, promotionToBrigadierGeneralDate, 1862-06-09]
-
A.
promotedToLieutenantGeneral
Indicates that an entity has been elevated in rank to the position of lieutenant general.
-
B.
appointedBrigadierGeneral
chosen
Indicates that an entity has been formally promoted or assigned to the military rank of Brigadier General.
-
C.
militaryRankDate
Indicates the date on which an entity attained, held, or was recorded with a particular military rank.
-
D.
promotedToGeneral
Indicates that an individual has been elevated in rank to the position or title of general.
-
E.
promotedToMajorGeneralCSA
Indicates that a person was elevated in rank to become a major general in the Confederate States Army.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 1:06 p.m.