Triple

T15693759
Position Surface form Disambiguated ID Type / Status
Subject Old Moster Church E380401 entity
Predicate near P350 FINISHED
Object Mosterhamn E1170719 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: Mosterhamn | Statement: [Old Moster Church, near, Mosterhamn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mosterhamn
Context triple: [Old Moster Church, near, Mosterhamn]
  • A. Mosterhamn chosen
    Mosterhamn is a coastal village in Vestland county, Norway, known for its maritime heritage and historic church site.
  • B. Holmsund
    Holmsund is a coastal locality in northern Sweden, known as a port town near Umeå on the Gulf of Bothnia.
  • C. Finnhamn
    Finnhamn is a popular island destination in the Stockholm archipelago known for its natural scenery, guest harbor, and outdoor recreation opportunities.
  • D. Steenodde
    Steenodde is a small coastal village on the North Sea island of Amrum in Germany, known for its tranquil atmosphere and maritime surroundings.
  • E. Eiderstedt
    Eiderstedt is a low-lying peninsula on Germany’s North Sea coast known for its dike-protected marshlands, agriculture, and coastal tourism.
  • 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_69d86d99e860819094b6957cde470f2c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e04f4f5a888190bd3681bcb9bbc02f completed April 16, 2026, 2:54 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffa9341a0c81909057dc338f218b85 completed May 9, 2026, 9:37 p.m.
Created at: April 10, 2026, 4:44 a.m.