Triple
T4928233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalinin Front |
E110628
|
entity |
| Predicate | headquartersLocation |
P62
|
FINISHED |
| Object | Kalinin |
E180855
|
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: Kalinin | Statement: [Kalinin Front, headquartersLocation, Kalinin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kalinin Context triple: [Kalinin Front, headquartersLocation, Kalinin]
-
A.
Kalinin
chosen
Kalinin is the former Soviet-era name of the Russian city now known as Tver, reflecting its renaming in honor of Bolshevik leader Mikhail Kalinin.
-
B.
Kuibyshev
Kuibyshev is the former Soviet name of the Russian city now known as Samara, a major industrial and administrative center on the Volga River.
-
C.
Kievskaya
Kievskaya is a prominent Moscow Metro station complex known for its ornate, Ukrainian-themed architecture and role as a major transfer hub.
-
D.
Kirovakan
Kirovakan is the former name of Vanadzor, a major industrial city in northern Armenia.
-
E.
Rizhskaya
Rizhskaya is a Moscow Metro station on the Big Circle Line serving the Rizhsky railway terminal area.
- 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7036d8e88190bc4be2975160da23 |
completed | March 20, 2026, 4:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be89e731a4819087bf2e55215654d9 |
completed | March 21, 2026, 12:07 p.m. |
Created at: March 20, 2026, 1:30 p.m.