Triple

T16821435
Position Surface form Disambiguated ID Type / Status
Subject Alt-Berlin E408901 entity
Predicate locatedOn P40 FINISHED
Object River Spree 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: River Spree | Statement: [Alt-Berlin, locatedOn, River Spree]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Spree
Context triple: [Alt-Berlin, locatedOn, River Spree]
  • A. River Spree chosen
    River Spree is a major river flowing through Berlin, Germany, known for shaping the city’s landscape and passing many historic and cultural landmarks.
  • B. Oder-Spree
    Oder-Spree is a rural district in the eastern German state of Brandenburg, known for its lakes, forests, and towns along the Oder and Spree rivers.
  • C. Dahme
    The Dahme is a river in eastern Germany that flows through Brandenburg and Berlin before joining the Spree.
  • D. Dahme
    Dahme is a small coastal town on the Baltic Sea in northern Germany, known for its beaches and seaside tourism.
  • E. Unstrut River
    The Unstrut River is a tributary of the Saale in central Germany, flowing through Thuringia and Saxony-Anhalt and known for its scenic valleys, vineyards, and historic towns.
  • 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_69d88394566c8190b3dcbdc72935f7fa completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b2e6b59c8190ad562a80e71ce54c completed April 18, 2026, 4:35 p.m.
Created at: April 10, 2026, 5:23 a.m.