Triple
T10192028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novogireyevo |
E238058
|
entity |
| Predicate | hasExitTo |
P29827
|
FINISHED |
| Object | Zeleny Prospekt |
E935845
|
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: Zeleny Prospekt | Statement: [Novogireyevo, hasExitTo, Zeleny Prospekt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zeleny Prospekt Context triple: [Novogireyevo, hasExitTo, Zeleny Prospekt]
-
A.
Zeleny Prospekt
chosen
Zeleny Prospekt is a major avenue in Moscow, Russia, known for running through several eastern districts and serving as an important local transport and residential corridor.
-
B.
Leninsky Prospekt
Leninsky Prospekt is a major avenue in Moscow, Russia, known for its wide thoroughfare, Soviet-era architecture, and prominent landmarks.
-
C.
Leninsky Prospekt
Leninsky Prospekt is a major avenue and transport artery in Saint Petersburg, Russia, known for connecting residential districts with the city’s broader road network.
-
D.
Michurinsky Prospekt
Michurinsky Prospekt is a metro station on Moscow’s Big Circle Line serving the Michurinsky Prospekt area in the city’s western district.
-
E.
Nakhimovsky Prospekt
Nakhimovsky Prospekt is a Moscow Metro station serving the Serpukhovsko–Timiryazevskaya Line in the south of Moscow.
- 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_69ca84de1b208190bf17bb305b002605 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdedc4fb808190aae2e4b84be96f83 |
completed | April 2, 2026, 4:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ee85e044e881909d426f7121dd89e1 |
completed | April 26, 2026, 9:38 p.m. |
Created at: March 30, 2026, 9:13 p.m.