Triple
T27977683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uranus encirclement at Stalingrad |
E706534
|
entity |
| Predicate | frontUsed |
P166472
|
FINISHED |
| Object | Southwestern Front |
—
|
NE NERFINISHED |
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: Southwestern Front | Statement: [Uranus encirclement at Stalingrad, frontUsed, Southwestern Front]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontUsed Context triple: [Uranus encirclement at Stalingrad, frontUsed, Southwestern Front]
-
A.
frontIn
Indicates that one entity is positioned directly in front of another entity in space or sequence.
-
B.
frontStatus
Indicates the current state or condition of something as presented or visible at the front (e.g., front-facing side, interface, or position).
-
C.
frontHeld
Indicates that one entity is being held in front of another entity or reference point.
-
D.
frontOf
Indicates that one entity is positioned directly before another along a primary viewing or movement direction.
-
E.
frontsUsedOn
Indicates that one entity uses or employs the front side or front-facing part of another entity.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6622808b48190bbabcc75288ab031 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f6617a7e7c81908cfac4a2250797ee |
completed | May 2, 2026, 8:41 p.m. |
Created at: April 27, 2026, 7:42 p.m.