Triple
T5618169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Donelson campaign |
E147529
|
entity |
| Predicate | confederatePrisonersTaken |
P65452
|
FINISHED |
| Object | over 12,000 |
—
|
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: over 12,000 | Statement: [Fort Donelson campaign, confederatePrisonersTaken, over 12,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confederatePrisonersTaken Context triple: [Fort Donelson campaign, confederatePrisonersTaken, over 12,000]
-
A.
confederateCasualtiesAndLosses
Indicates the number or extent of casualties and material losses suffered by Confederate forces in a conflict or engagement.
-
B.
commandingConfederateForces
Indicates that one entity holds the role or responsibility of directing and leading the military operations of the Confederate forces in relation to another entity.
-
C.
carriedPrisonersFrom
Indicates that an entity transported prisoners away from a specified origin location or source.
-
D.
opponentInAmericanCivilWar
Indicates that two entities were on opposing sides in the American Civil War.
-
E.
positionWithinConfederacy
Indicates that one entity holds a specific role, rank, or status within a confederated group or alliance of entities.
- 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_69c00905d4588190bd967842bbcf2219 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c021dd5d0081909d18d16596fac507 |
completed | March 22, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f40df64819089a659ea00a835ef |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:40 p.m.