Triple
T14430198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Арбатско-Покровская линия |
E357804
|
entity |
| Predicate | имеетСтанцию |
P726
|
FINISHED |
| Object | Арбатская |
E332773
|
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: Арбатская | Statement: [Арбатско-Покровская линия, имеетСтанцию, Арбатская]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Арбатская Context triple: [Арбатско-Покровская линия, имеетСтанцию, Арбатская]
-
A.
Arbatskaya
chosen
Arbatskaya is a Moscow Metro station located in the city center, known for its deep-level construction and ornate, grand architectural design.
-
B.
Tverskaya
Tverskaya is a Moscow Metro station located in the city center, serving the busy Tverskaya Street area with access to major commercial and cultural sites.
-
C.
Савёловская
Савёловская is a Moscow Metro station serving the city's rail and subway network.
-
D.
Tverskoy Boulevard
Tverskoy Boulevard is one of Moscow’s historic central boulevards, known for its tree-lined promenade, cultural landmarks, and role as part of the city’s Boulevard Ring.
-
E.
Izmailovskaya
Izmailovskaya was the original name of a Moscow Metro station later renamed Partizanskaya, located on the Arbatsko–Pokrovskaya line.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de914570f08190b1c7c1c57a0cb476 |
completed | April 14, 2026, 7:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd5bd1c4d0819085edb9ed22128b68 |
completed | May 8, 2026, 3:43 a.m. |
Created at: April 10, 2026, 1:18 a.m.