Triple
T4295414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 6th Army |
E99698
|
entity |
| Predicate | approximateStrengthAtStalingrad |
P11878
|
FINISHED |
| Object | over 250000 men |
—
|
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 250000 men | Statement: [6th Army, approximateStrengthAtStalingrad, over 250000 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateStrengthAtStalingrad Context triple: [6th Army, approximateStrengthAtStalingrad, over 250000 men]
-
A.
casualtiesAtStalingrad
Indicates that an entity experienced casualties (killed, wounded, or missing) in connection with the Battle of Stalingrad.
-
B.
locationDuringStalingrad
Indicates that an entity was located at a specific place during the time period of the Battle of Stalingrad.
-
C.
roleAtStalingrad
Indicates the specific role, position, or function an entity held in relation to the Battle of Stalingrad.
-
D.
PrussianStrengthApprox
Indicates an approximate assessment or estimation of the strength or power associated with Prussia in a given context.
-
E.
warTimeStrengthApprox
chosen
Indicates an approximate measure of an entity’s military strength or capacity during a time of 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35085b864819086cf726285384566 |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.