Triple
T16243745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsanger |
E394315
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Karasjok |
E365882
|
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: Karasjok | Statement: [Porsanger, borders, Karasjok]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Karasjok Context triple: [Porsanger, borders, Karasjok]
-
A.
Karasjok
chosen
Karasjok is a municipality in northern Norway known as a cultural and political center for the Sámi people.
-
B.
Longyearbyen
Longyearbyen is the world’s northernmost permanent settlement and the largest town in the Norwegian Arctic archipelago of Svalbard.
-
C.
Andenes
Andenes is a small coastal village in northern Norway known for its Arctic location, fishing heritage, and whale-watching tourism.
-
D.
Narvik
Narvik is a port town in northern Norway known for its strategic importance during World War II and as the site of major naval and land battles.
-
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 (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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24560060c8190ace4f4c0bd0d886d |
completed | April 17, 2026, 2:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a000edf64a88190a9dd0c591c742977 |
completed | May 10, 2026, 4:51 a.m. |
Created at: April 10, 2026, 5:04 a.m.