Triple
T5534714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eysturoy |
E145131
|
entity |
| Predicate | hasVillage |
P4011
|
FINISHED |
| Object | Strendur |
E529206
|
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: Strendur | Statement: [Eysturoy, hasVillage, Strendur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Strendur Context triple: [Eysturoy, hasVillage, Strendur]
-
A.
Strendur
chosen
Strendur is a village and important local settlement on the island of Eysturoy in the Faroe Islands.
-
B.
Inntal
Inntal is a major Alpine valley in western Austria carved by the Inn River, known for its scenic landscapes and important transport routes.
-
C.
Gautar
Gautar is the Old Norse name for the Geats, a North Germanic people historically inhabiting what is now southern Sweden.
-
D.
Brattahlid
Brattahlid was the main Norse settlement and estate of Erik the Red in southern Greenland, serving as a central hub of the medieval Greenlandic Norse colony.
-
E.
Fræna
Fræna is a former coastal municipality in western Norway known for its rugged shoreline, fishing communities, and scenic North Atlantic landscapes.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fa0141c81909a216be9f48d64e1 |
completed | March 22, 2026, 4:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c04ce1bce4819095559af19cf072f8 |
completed | March 22, 2026, 8:11 p.m. |
Created at: March 22, 2026, 3:34 p.m.