Triple

T16428544
Position Surface form Disambiguated ID Type / Status
Subject Frauentor E399009 entity
Predicate hasNearbyPlace P3449 FINISHED
Object Königstor E1217728 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: Königstor | Statement: [Frauentor, hasNearbyPlace, Königstor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Königstor
Context triple: [Frauentor, hasNearbyPlace, Königstor]
  • A. Königstor chosen
    Königstor is a historic city gate in Nuremberg, Germany, that forms part of the medieval fortifications surrounding the old town.
  • B. Rieder Tor
    Rieder Tor is a historic city gate in Donauwörth, Germany, and one of the town’s best-known architectural landmarks.
  • C. Schottentor
    Schottentor is a historic former city gate area in Vienna that now serves as a major public transport hub and landmark at the edge of the Innere Stadt.
  • D. Frauentor
    Frauentor is a historic city gate in Nuremberg, Germany, notable as one of the main entrances through the medieval fortifications into the old town.
  • E. Schlesisches Tor
    Schlesisches Tor is a historic U-Bahn station and well-known urban landmark in Berlin’s Kreuzberg district, noted for its distinctive elevated railway architecture and vibrant surrounding nightlife.
  • 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_69d87f2b9024819085c20e52de95d583 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e328fc223c8190bbed29907351a6f6 completed April 18, 2026, 6:47 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00758847948190b616cc85e208ee61 completed May 10, 2026, 12:09 p.m.
Created at: April 10, 2026, 5:09 a.m.