Triple
T21328992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bureya River |
E525844
|
entity |
| Predicate | nearSettlement |
P3883
|
FINISHED |
| Object | Novobureysky |
—
|
NE NERFINISHED |
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: Novobureysky | Statement: [Bureya River, nearSettlement, Novobureysky]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Novobureysky Context triple: [Bureya River, nearSettlement, Novobureysky]
-
A.
Novobureysky
chosen
Novobureysky is an urban-type settlement in Amur Oblast, Russia, situated near the confluence of the Bureya River.
-
B.
Borovitskaya
Borovitskaya is a Moscow Metro station located in the city center, providing key interchange access between several central lines.
-
C.
Novoyasenevskaya
Novoyasenevskaya is a Moscow Metro station located in the south of the city, serving as a terminal stop on the Kaluzhsko–Rizhskaya line near the Bitsevsky Park area.
-
D.
Kryukovo
Kryukovo is a railway station and suburban district in Zelenograd, Moscow, serving as a key commuter hub on the Leningradsky suburban rail line.
-
E.
Chertanovskaya
Chertanovskaya is a Moscow Metro station serving the Chertanovo district in the city’s south.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b51b90788190a4dd823d962626da |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7ab4f95fc819087eb32dca7da689a |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 16, 2026, 4:42 p.m.