Triple
T22045919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Funningsfjørður |
E544762
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Gjógv |
—
|
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: Gjógv | Statement: [Funningsfjørður, nearbySettlement, Gjógv]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gjógv Context triple: [Funningsfjørður, nearbySettlement, Gjógv]
-
A.
Gjógv
chosen
Gjógv is a small, picturesque village on the Faroe Islands’ island of Eysturoy, known for its dramatic sea-filled gorge and traditional turf-roofed houses.
-
B.
Slíðrugtanni
Slíðrugtanni is an alternative name for Gullinbursti, the golden-bristled boar associated with the Norse god Freyr.
-
C.
Gestaþáttr
Gestaþáttr is a section of the Old Norse poem Hávamál that offers practical wisdom and ethical guidelines for guests and hosts in Viking Age society.
-
D.
Hjálmar
Hjálmar is a masculine given name of Old Norse origin, traditionally used in Scandinavian countries.
-
E.
Erlingr
Erlingr is a variant form of the Scandinavian given name Erling, traditionally associated with Norse and Germanic origins.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1282e647481908e054b3ad19e2c15 |
completed | April 28, 2026, 9:35 p.m. |
Created at: April 16, 2026, 8:26 p.m.