Triple
T2331585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arbatsko–Pokrovskaya Line |
E44213
|
entity |
| Predicate | hasStation |
P35
|
FINISHED |
| Object | Kurskaya |
E258198
|
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: Kurskaya | Statement: [Arbatsko–Pokrovskaya Line, hasStation, Kurskaya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kurskaya Context triple: [Arbatsko–Pokrovskaya Line, hasStation, Kurskaya]
-
A.
Kurskaya
chosen
Kurskaya is a Moscow Metro station on the Koltsevaya (Circle) Line, serving as a major transfer hub in the city’s rapid transit network.
-
B.
Krasnov
Krasnov is a Russian surname borne by various notable figures in military, political, and cultural history.
-
C.
Sverdlov
Sverdlov is a Russian surname most notably associated with Yakov Sverdlov, a prominent Bolshevik leader during the early Soviet period.
-
D.
Dmitrovskaya
Dmitrovskaya is a Moscow Metro station on the Serpukhovsko–Timiryazevskaya Line serving the northern part of the city.
-
E.
Komsomolskaya
Komsomolskaya is one of Moscow Metro’s most famous and ornate stations, renowned for its grand Baroque-style decor and elaborate mosaics.
- 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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abc669956881908b8d9784d6a06acf |
completed | March 7, 2026, 6:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af905b6cfc8190a7c3b51f121cdb18 |
completed | March 10, 2026, 3:30 a.m. |
Created at: March 4, 2026, 7:51 p.m.