Triple
T12292463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prazhskaya |
E292995
|
entity |
| Predicate | hasAdjacentStation |
P231
|
FINISHED |
| Object | Yuzhnaya |
E239691
|
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: Yuzhnaya | Statement: [Prazhskaya, hasAdjacentStation, Yuzhnaya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yuzhnaya Context triple: [Prazhskaya, hasAdjacentStation, Yuzhnaya]
-
A.
Yuzhnaya
chosen
Yuzhnaya is a Moscow Metro station on the Serpukhovsko–Timiryazevskaya Line serving the southern part of the city.
-
B.
Yuzhne
Yuzhne is a port city on the Black Sea coast of southern Ukraine, known for its major industrial and maritime facilities.
-
C.
Yura
Yura is a common Slavic diminutive form of the male given name Yuri (or Yuriy), often used as a familiar or affectionate nickname.
-
D.
Nagatinskaya
Nagatinskaya is a Moscow Metro station serving the Serpukhovsko–Timiryazevskaya Line in the Nagatinsky Zaton area of southern Moscow.
-
E.
Yamskaya
Yamskaya is a name element associated with several historic streets and districts in Moscow, traditionally linked to coachmen’s settlements along major travel routes.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d22ba488190914342fa7e69e159 |
completed | April 10, 2026, 3:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e775dac819099d44b61cbccc109 |
completed | May 2, 2026, 3:55 p.m. |
Created at: April 8, 2026, 9:52 p.m.