Triple

T2136264
Position Surface form Disambiguated ID Type / Status
Subject Brandenburg E46660 entity
Predicate hasCity P316 FINISHED
Object Frankfurt (Oder) E150125 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: Frankfurt (Oder) | Statement: [Brandenburg, hasCity, Frankfurt (Oder)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Frankfurt (Oder)
Context triple: [Brandenburg, hasCity, Frankfurt (Oder)]
  • A. Frankfurt (Oder) chosen
    Frankfurt (Oder) is a German city on the Oder River at the Polish border, known as a historic university and trade center in the state of Brandenburg.
  • B. Görlitz
    Görlitz is a historic city in eastern Germany on the Lusatian Neisse River, known for its well-preserved old town and role as a popular film location.
  • C. Cottbus
    Cottbus is a city in eastern Germany known as a regional center for science and technology, including aerospace research.
  • D. Oppeln
    Oppeln is the historical German name for the city of Opole, a major cultural and administrative center in southwestern Poland’s Silesia region.
  • E. Neustrelitz
    Neustrelitz is a town in northeastern Germany known for hosting a key research center of the German Aerospace Center (DLR), particularly focused on satellite data and space-related technologies.
  • 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_69a88a174ab48190a5db20c132e5dccf completed March 4, 2026, 7:37 p.m.
NER Named-entity recognition batch_69abbdc4ce8c81908d143d5451681e6a completed March 7, 2026, 5:55 a.m.
NED1 Entity disambiguation (via context triple) batch_69b1f84713348190857e24a57a717cf9 completed March 11, 2026, 11:18 p.m.
Created at: March 4, 2026, 7:44 p.m.