Triple
T9719453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amusement Field |
E235425
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Moyka River |
E32085
|
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: Moyka River | Statement: [Amusement Field, adjacentTo, Moyka River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moyka River Context triple: [Amusement Field, adjacentTo, Moyka River]
-
A.
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.
-
B.
Moskva River
The Moskva River is a major waterway in western Russia that flows through and gives its name to the capital city, Moscow.
-
C.
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.
-
D.
Okhta River
The Okhta River is a tributary waterway in northwestern Russia that flows through Saint Petersburg before joining the Neva River.
-
E.
Moika River
chosen
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.
- 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_69ca84d0123c819096f9dc3b6abb0881 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e4022c4819097455f14dd9b1a77 |
completed | April 1, 2026, 10:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d25753fec48190927e8d96efd2df54 |
completed | April 5, 2026, 12:36 p.m. |
Created at: March 30, 2026, 8:20 p.m.