Triple
T843672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Square |
E18230
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Moskva River |
E14309
|
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: Moskva River | Statement: [Red Square, locatedNear, Moskva River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moskva River Context triple: [Red Square, locatedNear, Moskva River]
-
A.
Moskva River
chosen
The Moskva River is a major waterway in western Russia that flows through and gives its name to the capital city, Moscow.
-
B.
Moika River
The Moika River is a small, historic waterway in central Saint Petersburg, Russia, lined with notable palaces and landmarks and forming part of the city’s iconic canal network.
-
C.
Bolshaya Nevka
Bolshaya Nevka is a major distributary channel of the Neva River in Saint Petersburg, Russia, forming part of the city’s intricate river and canal network.
-
D.
Fontanka River
The Fontanka River is a major distributary of the Neva in Saint Petersburg, Russia, known for its historic embankments, bridges, and role in defining the city’s central layout.
-
E.
Yauza River
The Yauza River is a small river in Moscow, Russia, that flows through the city’s northeastern districts before joining the Moskva River.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac07fedc8190ab05595f25c1792f |
completed | March 1, 2026, 9:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac5e95e25881909c3e167417c0ae47 |
completed | March 7, 2026, 5:21 p.m. |
Created at: March 1, 2026, 7:38 p.m.