Triple
T5604600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leningradsky Prospekt |
E147201
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Leningrad |
E90774
|
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: Leningrad | Statement: [Leningradsky Prospekt, namedAfter, Leningrad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leningrad Context triple: [Leningradsky Prospekt, namedAfter, Leningrad]
-
A.
Leningrad
chosen
Leningrad, now known as Saint Petersburg, is a major Russian city on the Baltic Sea that served as the imperial capital and endured a devastating World War II siege.
-
B.
Stalino
Stalino was the Soviet-era name of the industrial city now known as Donetsk in eastern Ukraine.
-
C.
Petrovgrad
Petrovgrad was the former name of the Serbian city now known as Zrenjanin, located in the Vojvodina region.
-
D.
Odintsovo
Odintsovo is a town in western Russia that serves as an important suburban center just outside Moscow.
-
E.
Brest Fortress
Brest Fortress is a historic 19th-century Russian fortress in Brest, Belarus, renowned for its fierce Soviet resistance during the early days of the German invasion in World War II.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020f9408481908cf006074c726301 |
completed | March 22, 2026, 5:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0287649cc8190ae356790dd993973 |
completed | March 22, 2026, 5:35 p.m. |
Created at: March 22, 2026, 3:39 p.m.