Triple
T12398015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krestovsky Bridge |
E296170
|
entity |
| Predicate | waterway |
P1778
|
FINISHED |
| Object | Malaya Nevka |
E60916
|
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: Malaya Nevka | Statement: [Krestovsky Bridge, waterway, Malaya Nevka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Malaya Nevka Context triple: [Krestovsky Bridge, waterway, Malaya Nevka]
-
A.
Malaya Nevka
chosen
Malaya Nevka is a distributary channel of the Neva River in Saint Petersburg, Russia, forming part of the city’s intricate river and canal network.
-
B.
Navalnaya
Navalnaya is the surname of Yulia Navalnaya, a Russian public figure and the widow of opposition leader Alexei Navalny.
-
C.
Rizhskaya
Rizhskaya is a Moscow Metro station on the Big Circle Line serving the Rizhsky railway terminal area.
-
D.
Nakhimovskaya
Nakhimovskaya is an alternative form of the Russian place name Nakhimovskoye, typically reflecting feminine grammatical gender in Russian toponymy.
-
E.
Komsomolskaya
Komsomolskaya is one of Moscow Metro’s most famous and ornate stations, renowned for its grand Baroque-style decor and elaborate mosaics.
- 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_69d6ad9f464c81909db36d7e96e34b9e |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fd448f08190af425a569d7ed158 |
completed | April 10, 2026, 6:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f63480a8bc8190885130f63a3ec761 |
completed | May 2, 2026, 5:29 p.m. |
Created at: April 8, 2026, 9:54 p.m.