Triple
T982433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Gettysburg |
E21198
|
entity |
| Predicate | ConfederateStrength |
P1404
|
FINISHED |
| Object | approximately 71,000 soldiers |
—
|
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: approximately 71,000 soldiers | Statement: [Battle of Gettysburg, ConfederateStrength, approximately 71,000 soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ConfederateStrength Context triple: [Battle of Gettysburg, ConfederateStrength, approximately 71,000 soldiers]
-
A.
positionWithinConfederacy
Indicates that one entity holds a specific role, rank, or status within a confederated group or alliance of entities.
-
B.
combatantStrength
chosen
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
-
C.
positionOnConfederateLeadership
Indicates a stance or view an entity holds regarding the leadership of the Confederate side in a given conflict or historical context.
-
D.
opponentInAmericanCivilWar
Indicates that two entities were on opposing sides in the American Civil War.
-
E.
confederation
Indicates a formal union or alliance between multiple entities that retain their individual autonomy while cooperating under a shared framework or agreement.
- 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b49284ac8190b1d7c828d728893c |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2aa219081908a6b0ef786b4aa52 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.