Triple

T11161893
Position Surface form Disambiguated ID Type / Status
Subject Yantra River E264055 entity
Predicate hasBridge P386 FINISHED
Object Byala Bridge E346276 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: Byala Bridge | Statement: [Yantra River, hasBridge, Byala Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Byala Bridge
Context triple: [Yantra River, hasBridge, Byala Bridge]
  • A. Byala Bridge chosen
    Byala Bridge is a historic 19th-century stone arch bridge in Bulgaria, renowned for its elegant architecture and engineering across the Yantra River.
  • B. Prachechny Bridge
    Prachechny Bridge is a historic stone bridge in Saint Petersburg, Russia, spanning the Fontanka River near the former imperial laundry buildings.
  • C. Torgovy Bridge
    Torgovy Bridge is a historic pedestrian bridge spanning the Griboyedov Canal in Saint Petersburg, Russia.
  • D. Birzhevoy Bridge
    Birzhevoy Bridge is a bascule bridge in Saint Petersburg, Russia, spanning the Neva River and connecting Vasilyevsky Island with the Petrogradsky side near the historic Stock Exchange.
  • E. Sadovy Bridge
    Sadovy Bridge is a pedestrian bridge spanning the Griboyedov Canal in Saint Petersburg, Russia, known for its elegant design and role in the city’s historic urban landscape.
  • 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_69d6aa9ccddc8190868998c8b7beb060 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8832fe88190a74d81f9ed547baa completed April 9, 2026, 5:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69e55630478c8190aeee4cc219209ccb completed April 19, 2026, 10:24 p.m.
Created at: April 8, 2026, 9:29 p.m.