Triple

T20216471
Position Surface form Disambiguated ID Type / Status
Subject N331 E495139 entity
Predicate connectsCity P4245 FINISHED
Object Marknesse 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: Marknesse | Statement: [N331, connectsCity, Marknesse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Marknesse
Context triple: [N331, connectsCity, Marknesse]
  • A. Marknesse chosen
    Marknesse is a village in the Dutch province of Flevoland, known for its role in land reclamation history and its proximity to former hydraulic engineering test facilities.
  • B. Avaldsnes
    Avaldsnes is a historic village in Rogaland county, Norway, known as one of the country’s oldest royal seats and a key center in Viking-era history.
  • C. Rungholt
    Rungholt is a legendary medieval North Sea town said to have been drowned by a storm tide, inspiring numerous myths and stories about a sunken city.
  • D. Stromness
    Stromness is a historic harbor town on the southwest coast of Orkney Mainland in Scotland, known for its stone-built waterfront and maritime heritage.
  • E. Lindesnes peninsula
    Lindesnes peninsula is the southernmost headland of mainland Norway, known for its rugged coastline and historic lighthouse.
  • 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_69da626cff80819097b530718a7c98b6 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66eda2f188190adf39d895e8b99f2 completed April 20, 2026, 6:22 p.m.
Created at: April 11, 2026, 11:39 p.m.