Triple
T7201284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balchug Island |
E168750
|
entity |
| Predicate | connectedBy |
P37
|
FINISHED |
| Object | Ordynsky Bridge |
E465689
|
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: Ordynsky Bridge | Statement: [Balchug Island, connectedBy, Ordynsky Bridge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ordynsky Bridge Context triple: [Balchug Island, connectedBy, Ordynsky Bridge]
-
A.
Torgovy Bridge
Torgovy Bridge is a historic pedestrian bridge spanning the Griboyedov Canal in Saint Petersburg, Russia.
-
B.
Pevchesky Bridge
Pevchesky Bridge is a historic pedestrian bridge in Saint Petersburg, Russia, known for spanning the Griboyedov Canal near the city’s central landmarks.
-
C.
Pevchesky Bridge
Pevchesky Bridge is a historic pedestrian bridge in Saint Petersburg, Russia, known for spanning the Moika River near the city’s central cultural and architectural landmarks.
-
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.
Yauzsky Bridge
chosen
Yauzsky Bridge is a road bridge in Moscow that spans the Yauza River, connecting central city districts and serving as part of the city’s historic transport infrastructure.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e94971508190bb38184c9af2fe51 |
completed | March 27, 2026, 8:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8de8efd648190b70b4299ecae32c7 |
completed | March 29, 2026, 8:10 a.m. |
Created at: March 27, 2026, 2:52 p.m.