Triple
T17720252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livoberezhna |
E442314
|
entity |
| Predicate | hasFormerName |
P65
|
FINISHED |
| Object | Livoberezhnaya |
—
|
NE NERFINISHED |
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: Livoberezhnaya | Statement: [Livoberezhna, hasFormerName, Livoberezhnaya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Livoberezhnaya Context triple: [Livoberezhna, hasFormerName, Livoberezhnaya]
-
A.
Livoberezhna
chosen
Livoberezhna is a metro station on the Kyiv Metro system, serving the left-bank area of Ukraine’s capital city.
-
B.
Novorybnaya
Novorybnaya is a small rural settlement located along the Khatanga River in the remote Arctic region of northern Siberia, Russia.
-
C.
Malyovitsa
Malyovitsa is a prominent peak in Bulgaria renowned for its rugged alpine scenery and popularity among climbers and hikers.
-
D.
Olkhovaya
Olkhovaya is a station on the Moscow Metro system, located near Prokshino on the same line.
-
E.
Borovitskaya
Borovitskaya is a Moscow Metro station located in the city center, providing key interchange access between several central lines.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4748520a881908dc3446d33236ff7 |
completed | April 19, 2026, 6:21 a.m. |
Created at: April 10, 2026, 10:07 a.m.