Triple
T5020592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montauban |
E112838
|
entity |
| Predicate | twinTown |
P1072
|
FINISHED |
| Object | Kursk |
E312116
|
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: Kursk | Statement: [Montauban, twinTown, Kursk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kursk Context triple: [Montauban, twinTown, Kursk]
-
A.
Kursk
chosen
Kursk is a historic city in western Russia known for the pivotal World War II Battle of Kursk and its role as an important regional industrial and cultural center.
-
B.
Kurskaya
Kurskaya is a Moscow Metro station on the Koltsevaya (Circle) Line, serving as a major transfer hub in the city’s rapid transit network.
-
C.
Kronstadt
Kronstadt is a historic Russian naval port and fortress city located on Kotlin Island near Saint Petersburg, long serving as a key base for the Russian Baltic Fleet.
-
D.
Petrovsk-Port
Petrovsk-Port was a significant port city in the Russian Empire’s Caucasus region, serving as an important commercial and strategic hub on the Caspian Sea.
-
E.
Rzhev
Rzhev is a historic town in western Russia known for its strategic location on the Volga River and as the site of major World War II battles.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd736399ac8190aa38efc4b4edc6a2 |
completed | March 20, 2026, 4:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be927f4ad0819096826f6cb141c90b |
completed | March 21, 2026, 12:43 p.m. |
Created at: March 20, 2026, 1:36 p.m.