Triple
T1190189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Vicksburg |
E25339
|
entity |
| Predicate | confederateStrengthApproximate |
P11878
|
FINISHED |
| Object | 30000 |
—
|
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: 30000 | Statement: [Siege of Vicksburg, confederateStrengthApproximate, 30000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confederateStrengthApproximate Context triple: [Siege of Vicksburg, confederateStrengthApproximate, 30000]
-
A.
positionWithinConfederacy
Indicates that one entity holds a specific role, rank, or status within a confederated group or alliance of entities.
-
B.
combatantStrength
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
-
C.
joinedConfederateStatesOfAmerica
Indicates that an entity became a member of, or formally aligned itself with, the Confederate States of America.
-
D.
warTimeStrengthApprox
chosen
Indicates an approximate measure of an entity’s military strength or capacity during a time of war.
-
E.
opponentInAmericanCivilWar
Indicates that two entities were on opposing sides in the American Civil War.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd58d8d88190b8d9c9c9de7f4e97 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.