Triple

T10949933
Position Surface form Disambiguated ID Type / Status
Subject St. Pauli E258698 entity
Predicate adjacentTo P224 FINISHED
Object Altona E785302 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: Altona | Statement: [St. Pauli, adjacentTo, Altona]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Altona
Context triple: [St. Pauli, adjacentTo, Altona]
  • A. Brunsbüttel
    Brunsbüttel is a German port town at the western entrance of the Kiel Canal on the North Sea coast of Schleswig-Holstein.
  • B. Altona, Holstein chosen
    Altona, Holstein was a historically significant town in the Duchy of Holstein (now part of Hamburg, Germany), known as an important commercial and cultural center under Danish rule.
  • C. Köpenick
    Köpenick is a historic, green district in southeastern Berlin known for its old town, baroque palace on the Dahme River, and extensive forests and lakes.
  • D. Fuhlsbüttel
    Fuhlsbüttel is a district in the northern German city of Hamburg best known for hosting the city’s international airport.
  • E. Nittendorf
    Nittendorf is a municipality in the Upper Palatinate region of Bavaria, Germany, situated west of the city of Regensburg.
  • 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_69d6aa88500c819097d7032ca578e74f completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d770ed2f1c819081ec58457f57889d completed April 9, 2026, 9:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69e23c4a75688190894c83b8964509a6 completed April 17, 2026, 1:57 p.m.
Created at: April 8, 2026, 9:23 p.m.