Triple
T15412406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apatity |
E368625
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Kirovsk |
E182067
|
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: Kirovsk | Statement: [Apatity, locatedNear, Kirovsk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kirovsk Context triple: [Apatity, locatedNear, Kirovsk]
-
A.
Kirovsk
chosen
Kirovsk is an industrial town in Russia’s Murmansk Oblast, known for its mining industry and location in the Khibiny Mountains on the Kola Peninsula.
-
B.
Kirovsk
Kirovsk is a small industrial town in northwestern Russia, situated near Saint Petersburg along the Neva River.
-
C.
Kirovskaya
Kirovskaya was the original name of the Moscow Metro station now known as Chistye Prudy.
-
D.
Kamyensk-Shakhtinsky
Kamyensk-Shakhtinsky is a city in southwestern Russia known as an industrial and transport center within Rostov Oblast.
-
E.
Kirovgrad
Kirovgrad is a small industrial town in Russia’s Ural region, historically associated with non-ferrous metal mining and processing.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ea600b48190a3dbca1a68a2a1cd |
completed | April 16, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00aade82788190a5f3cedbc22065c4 |
completed | May 10, 2026, 3:57 p.m. |
Created at: April 10, 2026, 3:20 a.m.