Triple
T12086071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South-Western Administrative Okrug |
E287809
|
entity |
| Predicate | hasMetroLine |
P17559
|
FINISHED |
| Object | Butovskaya line |
E47280
|
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: Butovskaya line | Statement: [South-Western Administrative Okrug, hasMetroLine, Butovskaya line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Butovskaya line Context triple: [South-Western Administrative Okrug, hasMetroLine, Butovskaya line]
-
A.
Butovskaya Line
chosen
The Butovskaya Line is a light metro line in the Moscow Metro system serving the Butovo district in the city’s south.
-
B.
Zhdanovskaya Line
Zhdanovskaya Line was the former name of a line of the Moscow Metro, later known as the Tagansko–Krasnopresnenskaya Line.
-
C.
Filevskaya Line
Filevskaya Line is one of the lines of the Moscow Metro, known for its partially surface-level sections and service to western districts of the city.
-
D.
Solntsevskaya Line
The Solntsevskaya Line is a line of the Moscow Metro system serving western and southwestern districts of Moscow with modern rapid transit connections.
-
E.
Oleksiivska line
The Oleksiivska line is one of the main lines of the Kharkiv Metro system in Kharkiv, Ukraine, serving several key residential and commercial districts of the city.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91514c78c8190bc1cd569e524e8b4 |
completed | April 10, 2026, 3:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60a6d74888190aab150f1ceb2e9f1 |
completed | May 2, 2026, 2:30 p.m. |
Created at: April 8, 2026, 9:48 p.m.