Triple

T6834533
Position Surface form Disambiguated ID Type / Status
Subject DESY E157416 entity
Predicate locatedIn P40 FINISHED
Object Zeuthen E621151 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: Zeuthen | Statement: [DESY, locatedIn, Zeuthen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zeuthen
Context triple: [DESY, locatedIn, Zeuthen]
  • A. Zeuthen chosen
    Zeuthen is a municipality in Brandenburg, Germany, known for hosting a major campus of the DESY particle physics research center.
  • B. Friedland
    Friedland is a town in present-day Pravdinsk, Russia, historically notable as the site of the decisive 1807 Napoleonic battle between French and Russian forces.
  • C. Friedland
    Friedland is a municipality in Lower Saxony, Germany, known for its historic border location and post-World War II refugee transit camp.
  • D. Zinnowitz
    Zinnowitz is a seaside resort town on Germany’s Baltic Sea coast, known for its sandy beaches, historic spa architecture, and tourism on the island of Usedom.
  • E. Rüngsdorf
    Rüngsdorf is a residential district in the southern part of Bonn, Germany, known for its scenic location along the Rhine and its affiliation with the Bad Godesberg borough.
  • 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_69c6882c53608190b99aebef079b23bd completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d67936288190829fedc3729aadd8 completed March 27, 2026, 7:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69c769e8e06881908763bba8f7b82a99 completed March 28, 2026, 5:40 a.m.
Created at: March 27, 2026, 2:18 p.m.