Triple

T21807891
Position Surface form Disambiguated ID Type / Status
Subject Långe Jan lighthouse E538394 entity
Predicate locatedAt P40 FINISHED
Object Ottenby 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: Ottenby | Statement: [Långe Jan lighthouse, locatedAt, Ottenby]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ottenby
Context triple: [Långe Jan lighthouse, locatedAt, Ottenby]
  • A. Ottenby chosen
    Ottenby is a nature reserve and historic estate at the southern tip of the Swedish island of Öland, known for its rich birdlife and coastal landscapes.
  • B. Hallingby
    Hallingby is a small village in the municipality of Ringerike in Buskerud county, Norway.
  • C. Thoralby
    Thoralby is a small rural village in the Yorkshire Dales of North Yorkshire, England, known for its traditional stone buildings and scenic surroundings.
  • D. Ingoldsby
    Ingoldsby is a small rural community located within the township of Minden Hills in Ontario, Canada.
  • E. Ormesby
    Ormesby is a suburban settlement within the borough of Redcar and Cleveland in North Yorkshire, England.
  • 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_69e0c473f0f8819086c9d1b4a143bd67 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f078047ca88190a0efa4bc7f2faf80 completed April 28, 2026, 9:04 a.m.
Created at: April 16, 2026, 6:53 p.m.