Triple

T22295571
Position Surface form Disambiguated ID Type / Status
Subject Sørvágur E551109 entity
Predicate hasNearbySettlement P4647 FINISHED
Object Sandavágur 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: Sandavágur | Statement: [Sørvágur, hasNearbySettlement, Sandavágur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sandavágur
Context triple: [Sørvágur, hasNearbySettlement, Sandavágur]
  • A. Sandavágur chosen
    Sandavágur is a picturesque coastal village on the island of Vágar in the Faroe Islands, known for its colorful houses, historic church, and scenic harbor views.
  • B. Vágur
    Vágur is a town and important fishing settlement on the island of Suðuroy in the Faroe Islands.
  • C. Sørvágur
    Sørvágur is a village on the Faroe Islands' island of Vágar, known for its coastal setting and proximity to Vágar Airport.
  • D. Leirvík
    Leirvík is a coastal village and important fishing community on the Faroe Islands, located on the island of Eysturoy.
  • E. Hvalvík
    Hvalvík is a small coastal village in the Faroe Islands known for its traditional wooden church and scenic fjord-side 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_69e11e45fb848190a1b2ae21296e3a5f completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1571fe76c8190a40b3679802a5475 completed April 29, 2026, 12:56 a.m.
Created at: April 16, 2026, 8:41 p.m.