Triple

T16227716
Position Surface form Disambiguated ID Type / Status
Subject Srokowo E393895 entity
Predicate historicalName P65 FINISHED
Object Drengfurt E1200855 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: Drengfurt | Statement: [Srokowo, historicalName, Drengfurt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Drengfurt
Context triple: [Srokowo, historicalName, Drengfurt]
  • A. Drengfurth chosen
    Drengfurth is the former German name of the town now known as Srokowo in northern Poland, historically part of East Prussia.
  • B. Drensteinfurt
    Drensteinfurt is a small town in North Rhine-Westphalia, Germany, known for its historic architecture and location in the Münsterland region.
  • C. Hemfurth
    Hemfurth is a village in central Germany best known for its proximity to the historic Eder Dam and the Edersee reservoir.
  • D. Stockheim
    Stockheim is a village and district of the town of Brackenheim in the Heilbronn district of Baden-Württemberg, Germany.
  • E. Arzdorf
    Arzdorf is a village and district of the municipality of Wachtberg in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
  • 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_69d87f204df88190a8f88923decf9835 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e23d2785f88190ae80d5d61129d3e5 completed April 17, 2026, 2:01 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0017ab10a48190afa19e74c0059427 completed May 10, 2026, 5:29 a.m.
Created at: April 10, 2026, 5:03 a.m.