Triple

T4149716
Position Surface form Disambiguated ID Type / Status
Subject Villa Tugendhat E89873 entity
Predicate locatedIn P40 FINISHED
Object Brno E47149 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: Brno | Statement: [Villa Tugendhat, locatedIn, Brno]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brno
Context triple: [Villa Tugendhat, locatedIn, Brno]
  • A. Brno chosen
    Brno is the second-largest city in the Czech Republic, known as a major cultural, educational, and industrial center in the historical region of Moravia.
  • B. Kolín
    Kolín is a historic industrial town and important transport hub on the Elbe River in the Central Bohemian Region of the Czech Republic.
  • C. Ostrava
    Ostrava is a major industrial and cultural city in the northeastern Czech Republic, near the borders with Poland and Slovakia.
  • D. Olomouc
    Olomouc is a historic city in the eastern Czech Republic known for its well-preserved old town, Baroque architecture, and UNESCO-listed Holy Trinity Column.
  • E. Plzeň
    Plzeň is a major city in western Bohemia in the Czech Republic, known for its brewing tradition and industrial heritage.
  • 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_69aed95a59a881909b26e70b42c6811a completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af0273a038819087db092da234e767 completed March 9, 2026, 5:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5db72503c81909e9cf69f23d093fc completed March 14, 2026, 10:04 p.m.
Created at: March 9, 2026, 3:43 p.m.