Triple

T22173683
Position Surface form Disambiguated ID Type / Status
Subject Waxholmsbolaget ferries E547986 entity
Predicate connects P390 FINISHED
Object Finnhamn 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: Finnhamn | Statement: [Waxholmsbolaget ferries, connects, Finnhamn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Finnhamn
Context triple: [Waxholmsbolaget ferries, connects, Finnhamn]
  • A. Finnhamn chosen
    Finnhamn is a popular island destination in the Stockholm archipelago known for its natural scenery, guest harbor, and outdoor recreation opportunities.
  • B. Grisslehamn
    Grisslehamn is a small coastal village in eastern Sweden known for its harbor, fishing heritage, and ferry connection to the Åland Islands.
  • C. Knarrviki
    Knarrviki is a village in Vestland county, Norway, serving as the main local hub and seat of government for Alver Municipality.
  • D. Foldrøyhamn
    Foldrøyhamn is a small coastal village in Bømlo Municipality in Vestland county, western Norway.
  • E. Mosterhamn
    Mosterhamn is a coastal village in Vestland county, Norway, known for its maritime heritage and historic church site.
  • 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_69e11e3d53f88190a2b690e3f25bb062 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12a6a9370819098ad65fede676c2b completed April 28, 2026, 9:45 p.m.
Created at: April 16, 2026, 8:34 p.m.