Triple

T8754512
Position Surface form Disambiguated ID Type / Status
Subject Nizhny Novgorod Cableway E208040 entity
Predicate cityServed P82 FINISHED
Object Bor E292089 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: Bor | Statement: [Nizhny Novgorod Cableway, cityServed, Bor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bor
Context triple: [Nizhny Novgorod Cableway, cityServed, Bor]
  • A. Bor chosen
    Bor is a town in Nizhny Novgorod Oblast, Russia, located on the left bank of the Volga River opposite the city of Nizhny Novgorod and known for its industrial and river transport significance.
  • B. Bor
    Bor is a major town in South Sudan’s Jonglei State, situated on the White Nile and serving as an important regional administrative and transport hub.
  • C. Bor
    Bor is a London Underground station serving the Borough area of Southwark in central London.
  • D. Bori
    Bori is a prominent urban center in Nigeria’s Rivers State, serving as an important commercial and administrative hub for the surrounding region.
  • E. Borotiam
    Borotiam is a village located on the atoll of Abaiang in the island nation of Kiribati in the central Pacific Ocean.
  • 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_69ca835cd6b08190bd7c63db92f53c86 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5dd83088819082cf54adc0c04243 completed March 31, 2026, 11:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf6f10aea48190bb63a4b2fdd72338 completed April 3, 2026, 7:41 a.m.
Created at: March 30, 2026, 6:39 p.m.