Triple

T6578129
Position Surface form Disambiguated ID Type / Status
Subject Skúvoy village E157221 entity
Predicate locatedOn P40 FINISHED
Object Skúvoy E157221 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: Skúvoy | Statement: [Skúvoy village, locatedOn, Skúvoy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Skúvoy
Context triple: [Skúvoy village, locatedOn, Skúvoy]
  • A. Skúvoy chosen
    Skúvoy is a small, sparsely populated island in the central Faroe Islands, known for its dramatic cliffs, rich birdlife, and traditional Faroese village.
  • B. Egegik, Alaska
    Egegik, Alaska is a small fishing community on the Alaska Peninsula known for its commercial salmon fishery in the Bristol Bay region.
  • C. Diomede, Alaska
    Diomede, Alaska is a small Inupiat village located on Little Diomede Island in the Bering Strait, known for its remote Arctic setting just miles from Russia’s Big Diomede Island.
  • D. Savoonga
    Savoonga is a remote Alaska Native village on St. Lawrence Island in the Bering Sea, known for its Siberian Yupik culture and subsistence hunting lifestyle.
  • E. Savoonga, Alaska
    Savoonga, Alaska is a remote, predominantly Siberian Yupik village located on St. Lawrence Island in the Bering Sea.
  • 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_69c6882b3a108190b3a9eb343ae4162c completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ae74fd90819091d67eec6381d5e0 completed March 27, 2026, 4:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6f78896b48190a8d993c207d01a7e completed March 27, 2026, 9:32 p.m.
Created at: March 27, 2026, 1:54 p.m.