Triple
T6195182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Maloyaroslavets |
E138491
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Kaluga |
E314023
|
NE 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: Kaluga | Statement: [Battle of Maloyaroslavets, near, Kaluga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kaluga Context triple: [Battle of Maloyaroslavets, near, Kaluga]
-
A.
Kaluga
chosen
Kaluga is a historic city in western Russia known as a regional administrative center and an important site in several Russian uprisings and military campaigns.
-
B.
Kirov
Kirov is the revolutionary pseudonym of Sergei Kirov, a prominent early Soviet political leader and close associate of Joseph Stalin.
-
C.
Kirov
Kirov is a town in Kaluga Oblast, Russia, known as a local administrative and industrial center.
-
D.
Sverdlovsk
Sverdlovsk is the former name of Yekaterinburg, a major industrial and cultural city in Russia’s Ural region.
-
E.
Oryol
Oryol was a notable warship of the Imperial Russian Navy, recognized for its role in Russia’s early modern naval history.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062443cec81909dc9bafea2f5e7d4 |
completed | March 22, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c70add5a788190a2b16839659f662b |
completed | March 27, 2026, 10:55 p.m. |
Created at: March 22, 2026, 4:19 p.m.