Triple

T3882376
Position Surface form Disambiguated ID Type / Status
Subject European route E6 E92854 entity
Predicate terminus P388 FINISHED
Object Kirkenes E95872 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: Kirkenes | Statement: [European route E6, terminus, Kirkenes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kirkenes
Context triple: [European route E6, terminus, Kirkenes]
  • A. Kirkenes chosen
    Kirkenes is a remote Arctic town in northeastern Norway, near the Russian border, known for its Barents Sea port, winter tourism, and role as a gateway to the far north.
  • B. Murmansk
    Murmansk is a major Arctic port city in northwestern Russia, known for its ice-free harbor and strategic military and shipping importance.
  • C. Vardø
    Vardø is a small coastal town in Norway’s far northeast, known as one of the country’s easternmost settlements and a historic Arctic gateway.
  • D. Severodvinsk
    Severodvinsk is a Russian port city on the White Sea, known as a major center for the construction and maintenance of nuclear submarines.
  • E. Karasjok
    Karasjok is a municipality in northern Norway known as a cultural and political center for the Sámi people.
  • 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_69aed9697de0819087c2559295ff3d12 completed March 9, 2026, 2:30 p.m.
NER Named-entity recognition batch_69aeec8e8b3481909617ca0e37f8a6d4 completed March 9, 2026, 3:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69b51c8983b88190a716987f44487d56 completed March 14, 2026, 8:30 a.m.
Created at: March 9, 2026, 3:20 p.m.