Triple

T19344738
Position Surface form Disambiguated ID Type / Status
Subject Schley E483844 entity
Predicate hasVariant P455 FINISHED
Object Schlei 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: Schlei | Statement: [Schley, hasVariant, Schlei]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schlei
Context triple: [Schley, hasVariant, Schlei]
  • A. Schlei chosen
    Schlei is a narrow Baltic Sea inlet in northern Germany that resembles a river and is known for its scenic landscapes and historic towns.
  • B. Wümme
    The Wümme is a river in northern Germany that flows through Lower Saxony and Bremen before joining with the Hamme to form the Lesum.
  • C. Ganderkesee
    Ganderkesee is a municipality in Lower Saxony, Germany, known for its rural character and proximity to the city of Bremen.
  • D. Edersee
    Edersee is a large artificial reservoir in northern Hesse, Germany, created by the Eder Dam and known for recreation, water sports, and its scenic surroundings.
  • E. Blausee
    Blausee is a small, crystal-clear alpine lake in the Swiss Bernese Oberland, famed for its striking blue waters and tranquil forest surroundings.
  • 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_69d8e8d244f8819080eb1f3491300db2 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e618598dc08190a723398dd6fe551d completed April 20, 2026, 12:13 p.m.
Created at: April 10, 2026, 1:34 p.m.