Triple

T19806933
Position Surface form Disambiguated ID Type / Status
Subject Kirov Oblast E475836 entity
Predicate hasCity P316 FINISHED
Object Kotelnich 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: Kotelnich | Statement: [Kirov Oblast, hasCity, Kotelnich]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kotelnich
Context triple: [Kirov Oblast, hasCity, Kotelnich]
  • A. Kotelnich chosen
    Kotelnich is a town in Kirov Oblast, Russia, known for its location on the Vyatka River and nearby rich fossil beds of Permian-period vertebrates.
  • B. Krasny Kut
    Krasny Kut is a small town in southwestern Russia known as an administrative and agricultural center within the Saratov region.
  • C. Kotelniki
    Kotelniki is a Moscow Metro station serving as the southeastern terminus of the Tagansko–Krasnopresnenskaya Line in the town of Kotelniki, just outside Moscow.
  • D. Krasnobród
    Krasnobród is a small town in southeastern Poland known for its historical role in World War II and as a local tourist and spa destination in the Roztocze region.
  • E. Kozelets
    Kozelets is an urban-type settlement in northern Ukraine, historically known as a local administrative and trading center.
  • 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_69d8e51bc4208190a1c57d8c5d1b15e4 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65428f5c48190be6ae0d6a77675d2 completed April 20, 2026, 4:28 p.m.
Created at: April 10, 2026, 1:49 p.m.