Triple
T21519644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiorthhamn |
E530938
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Longyearbyen |
—
|
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: Longyearbyen | Statement: [Hiorthhamn, locatedNear, Longyearbyen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Longyearbyen Context triple: [Hiorthhamn, locatedNear, Longyearbyen]
-
A.
Longyearbyen
chosen
Longyearbyen is the world’s northernmost permanent settlement and the largest town in the Norwegian Arctic archipelago of Svalbard.
-
B.
Karasjok
Karasjok is a municipality in northern Norway known as a cultural and political center for the Sámi people.
-
C.
Oymyakon
Oymyakon is a remote rural locality in Russia’s Sakha Republic known as one of the coldest permanently inhabited places on Earth.
-
D.
Barentsburg
Barentsburg is a Russian mining settlement on the Norwegian archipelago of Svalbard, known for its coal industry and Soviet-era character.
-
E.
Ivalo
Ivalo is a village in northern Finnish Lapland known as a key transport hub and gateway to the surrounding Arctic wilderness and tourism areas.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee884af0f08190bc1f3d70e57a325d |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 16, 2026, 6:26 p.m.