Triple

T11596389
Position Surface form Disambiguated ID Type / Status
Subject Dynamo Kursk E275011 entity
Predicate homeCity P263 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: [Dynamo Kursk, homeCity, Kursk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kursk
Context triple: [Dynamo Kursk, homeCity, 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. Sestroretsk
    Sestroretsk is a town in northwestern Russia, now part of Saint Petersburg, historically known for its arms factory and seaside resort area on the Gulf of Finland.
  • 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_69d6aae6b14c81908dc5a74bad7591f9 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d89549c870819086e16e9110bbad87 completed April 10, 2026, 6:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69e8a7cad108819082eebb3ca130f5b8 completed April 22, 2026, 10:49 a.m.
Created at: April 8, 2026, 9:38 p.m.