Triple

T16403804
Position Surface form Disambiguated ID Type / Status
Subject Altstadt (old town) of Nuremberg E398371 entity
Predicate hasPart P35 FINISHED
Object Frauentor E399009 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: Frauentor | Statement: [Altstadt (old town) of Nuremberg, hasPart, Frauentor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Frauentor
Context triple: [Altstadt (old town) of Nuremberg, hasPart, Frauentor]
  • A. Frauentor chosen
    Frauentor is a historic city gate in Nuremberg, Germany, notable as one of the main entrances through the medieval fortifications into 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. Hallesches Tor
    Hallesches Tor is a major Berlin U-Bahn interchange station in the Kreuzberg district, serving as a key hub for multiple subway lines.
  • E. Stadttor
    Stadttor is a prominent modern office and government building in Düsseldorf, Germany, known for its distinctive glass architecture and role as a landmark of the MedienHafen area.
  • 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_69d87f2950248190bc8ad9b9bebdc8c8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e327d12dc08190a5b497692b667ed7 completed April 18, 2026, 6:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00679a900c8190aeb7a273943bf553 completed May 10, 2026, 11:10 a.m.
Created at: April 10, 2026, 5:09 a.m.