Triple
T12987818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ust-Izhora |
E321814
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Otradnoye |
E455201
|
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: Otradnoye | Statement: [Ust-Izhora, locatedNear, Otradnoye]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Otradnoye Context triple: [Ust-Izhora, locatedNear, Otradnoye]
-
A.
Otradnoye
chosen
Otradnoye is a town in Russia located within the Leningrad (Saint Petersburg) region, known for its position along the Neva River and proximity to Saint Petersburg.
-
B.
Otradnoye
Otradnoye is a Moscow Metro station on the Serpukhovsko–Timiryazevskaya Line serving the Otradnoye District in northern Moscow.
-
C.
Yuzovka
Yuzovka was the original name of the industrial settlement in eastern Ukraine that later developed into the city of Donetsk.
-
D.
Kastornoye
Kastornoye is a locality in Russia historically notable as the namesake and focal area of the Voronezh–Kastornoye military offensive during World War II.
-
E.
Fedorovskoye
Fedorovskoye is a rural locality in Russia situated within the Tosnensky District of Leningrad Oblast.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e5f47ec8190b39107bc016f9824 |
completed | April 10, 2026, 10:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f73053a1888190a234e8c119a4202a |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 9, 2026, 8:41 p.m.