Triple
T5289715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governor of Svalbard |
E119711
|
entity |
| Predicate | seat |
P75
|
FINISHED |
| Object | Longyearbyen |
E146214
|
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: Longyearbyen | Statement: [Governor of Svalbard, seat, Longyearbyen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Longyearbyen Context triple: [Governor of Svalbard, seat, 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.
Gjoa Haven
Gjoa Haven is a small Inuit community in Nunavut, Canada, known as a historic Arctic settlement linked to polar exploration and the Northwest Passage.
- 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_69bd446de5648190b313a90bd96730d2 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd84dcd6908190b35bf9c371965bc9 |
completed | March 20, 2026, 5:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf06f066988190a3df7e270df84fdd |
completed | March 21, 2026, 9 p.m. |
Created at: March 20, 2026, 1:52 p.m.