Triple
T20028801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow–Kursk railway line |
E495063
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Kursk |
—
|
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: Kursk | Statement: [Moscow–Kursk railway line, connects, Kursk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kursk Context triple: [Moscow–Kursk railway line, connects, 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.
Kronstadt
Kronstadt is a historic Transylvanian city (now known as Brașov, Romania) renowned for its medieval fortifications and Saxon heritage.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662908df081909a6c8ccf0dd90fff |
completed | April 20, 2026, 5:29 p.m. |
Created at: April 11, 2026, 3:36 p.m.