Triple
T9100757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lefortovo |
E218144
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Lefortovo District |
E218144
|
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: Lefortovo District | Statement: [Lefortovo, serves, Lefortovo District]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lefortovo District Context triple: [Lefortovo, serves, Lefortovo District]
-
A.
Vrazhdebna district
Vrazhdebna district is a northeastern residential and industrial area of Sofia, Bulgaria, known for its proximity to Sofia Airport.
-
B.
Pravdinsky District
Pravdinsky District is an administrative district in Kaliningrad Oblast, Russia, centered around the town of Pravdinsk.
-
C.
Lefortovo
chosen
Lefortovo is a Moscow Metro station on the Big Circle Line serving the historic Lefortovo district of Russia’s capital.
-
D.
Vnukovo District
Vnukovo District is a municipal district in the western part of Moscow, Russia, known for encompassing Vnukovo International Airport and surrounding residential and industrial areas.
-
E.
Novokosino District
Novokosino District is a residential administrative area in the eastern part of Moscow, Russia, known for its modern housing developments and integration into the city’s metro network.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc9711babc8190a336812dd08d9c73 |
completed | April 1, 2026, 3:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0182d8ea08190b4337a77b47019a5 |
completed | April 3, 2026, 7:42 p.m. |
Created at: March 30, 2026, 7:15 p.m.