Triple
T16684707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route E8 |
E405429
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Skibotn |
E381853
|
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: Skibotn | Statement: [European route E8, passesThrough, Skibotn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Skibotn Context triple: [European route E8, passesThrough, Skibotn]
-
A.
Skibotn
chosen
Skibotn is a small village in northern Norway known for its clear skies and role as a center for astronomical observations.
-
B.
Solbo
Solbo is a locality within Botkyrka Municipality in Stockholm County, Sweden.
-
C.
Bjorli
Bjorli is a Norwegian village known for its ski resort and scenic mountain surroundings in Innlandet county.
-
D.
Enebakk
Enebakk is a rural municipality in Viken county, Norway, known for its forests, lakes, and proximity to the Oslo metropolitan area.
-
E.
Smedvig
Smedvig is a Norwegian family name most prominently associated with the Smedvig shipping and oil services business dynasty.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37d71a66881908c8d06cc074fdf29 |
completed | April 18, 2026, 12:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a008a422f8c8190873fd7089df8fbd4 |
completed | May 10, 2026, 1:38 p.m. |
Created at: April 10, 2026, 5:19 a.m.