Triple

T22401759
Position Surface form Disambiguated ID Type / Status
Subject Halligen Frisian E553777 entity
Predicate spokenIn P2266 FINISHED
Object Langeneß 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: Langeneß | Statement: [Halligen Frisian, spokenIn, Langeneß]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Langeneß
Context triple: [Halligen Frisian, spokenIn, Langeneß]
  • A. Langeneß chosen
    Langeneß is a small Hallig island in the Wadden Sea off the coast of Schleswig-Holstein, Germany, known for its low-lying landscape, traditional Frisian culture, and vulnerability to tidal flooding.
  • B. Lengenfeld
    Lengenfeld is a small town in the Free State of Saxony in eastern Germany, known as the birthplace of biblical scholar Constantin von Tischendorf.
  • C. Leuenberg
    Leuenberg is a village in Switzerland known as the site where major European Protestant churches concluded the Leuenberg Agreement on church fellowship.
  • D. Langenbach
    Langenbach is a municipality in Bavaria, Germany, situated in the Freising district north of Munich.
  • E. Langenbach
    Langenbach is a locality that forms one of the subdivisions of the town of Vöhrenbach in the Black Forest region of southwestern Germany.
  • 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_69e11e4da7048190b4387d422a9a0de5 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f158b4a96c8190838f5dda21c4d853 completed April 29, 2026, 1:02 a.m.
Created at: April 16, 2026, 8:46 p.m.