Triple

T10510462
Position Surface form Disambiguated ID Type / Status
Subject Troitsky Bridge E247897 entity
Predicate officialName P66 FINISHED
Object Troitsky Bridge E247897 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: Troitsky Bridge | Statement: [Troitsky Bridge, officialName, Troitsky Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Troitsky Bridge
Context triple: [Troitsky Bridge, officialName, Troitsky Bridge]
  • A. Troitsky Bridge chosen
    Troitsky Bridge is a historic steel arch bridge in Saint Petersburg, Russia, spanning the Neva River and connecting the city center with the Petrograd Side.
  • B. Rubtsovsky Bridge
    Rubtsovsky Bridge is a road bridge in Moscow, Russia, carrying traffic across the Yauza River.
  • C. Semënovsky Bridge
    Semënovsky Bridge is a historic stone bridge in Saint Petersburg, Russia, spanning the Fontanka River and forming part of the city’s central embankment network.
  • D. Obukhovsky Bridge
    Obukhovsky Bridge is a historic road bridge in Saint Petersburg, Russia, known for carrying traffic across the Fontanka River near the city center.
  • E. Kolomyazhsky Bridge
    Kolomyazhsky Bridge is a road bridge in Saint Petersburg, Russia, spanning the Malaya Nevka River and connecting parts of the city’s Primorsky District.
  • 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_69d381c4aa948190942e1d803143fb0e completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d509b542088190868531f84deaf9e4 completed April 7, 2026, 1:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69d8dcee1db081908c791867e2438d30 completed April 10, 2026, 11:20 a.m.
Created at: April 6, 2026, 12:27 p.m.