Triple
T13555705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gisund Bridge |
E323766
|
entity |
| Predicate | regionServed |
P82
|
FINISHED |
| Object | Senja |
E79491
|
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: Senja | Statement: [Gisund Bridge, regionServed, Senja]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Senja Context triple: [Gisund Bridge, regionServed, Senja]
-
A.
Senja
chosen
Senja is Norway’s second-largest island, renowned for its dramatic coastal mountains, fishing villages, and scenic Arctic landscapes.
-
B.
Bilibino
Bilibino is a small town in Russia’s Far East best known for hosting one of the world’s northernmost nuclear power plants.
-
C.
Ruka
Ruka is a major Finnish ski resort and year-round outdoor destination located in northern Finland’s Kuusamo region.
-
D.
Somero
Somero is a small town and municipality in southwestern Finland known for its rural landscapes and agricultural heritage.
-
E.
Mayen
Mayen is a surname most notably borne by Dutch seafarer and explorer Jan Jacobszoon Mayen, after whom the Arctic island of Jan Mayen is named.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaff3063c8190bd20149b3f7df352 |
completed | April 12, 2026, 2:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f794281fb48190882f164df1def07e |
completed | May 3, 2026, 6:30 p.m. |
Created at: April 9, 2026, 9:47 p.m.