Triple
T21450890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Funningur |
E529203
|
entity |
| Predicate | hasCoastlineOn |
P212
|
FINISHED |
| Object | Funningsfjørður |
—
|
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: Funningsfjørður | Statement: [Funningur, hasCoastlineOn, Funningsfjørður]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Funningsfjørður Context triple: [Funningur, hasCoastlineOn, Funningsfjørður]
-
A.
Funningsfjørður
chosen
Funningsfjørður is a scenic fjord on the Faroe Islands’ island of Eysturoy, known for its steep surrounding mountains and traditional coastal settlements.
-
B.
Fuglafjørður
Fuglafjørður is a fishing town and important industrial port on the island of Eysturoy in the Faroe Islands.
-
C.
Hovsfjørður
Hovsfjørður is a coastal fjord in the Faroe Islands known for its scenic shoreline near the village of Hov on the island of Suðuroy.
-
D.
Kalsoyarfjørður
Kalsoyarfjørður is a narrow sea channel in the Faroe Islands that separates the island of Kalsoy from its neighboring islands.
-
E.
Oyndarfjørður
Oyndarfjørður is a small coastal village in the Faroe Islands, situated on the island of Eysturoy and known for its traditional turf-roofed houses and scenic fjord setting.
- 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_69e0c457579481909db68053ed99750c |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9d33e648190864b0ef5acf36659 |
completed | April 23, 2026, 9:43 a.m. |
Created at: April 16, 2026, 6:06 p.m.