Triple

T19846319
Position Surface form Disambiguated ID Type / Status
Subject Dejvice campus E476868 entity
Predicate locatedIn P40 FINISHED
Object Dejvice NE NERFINISHED

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: Dejvice | Statement: [Dejvice campus, locatedIn, Dejvice]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dejvice
Context triple: [Dejvice campus, locatedIn, Dejvice]
  • A. Dejvice chosen
    Dejvice is a prominent residential and university district in Prague known for its modernist architecture, green spaces, and the campus of the Czech Technical University.
  • B. Dejvická
    Dejvická is a metro station in Prague that serves as a key transport hub in the Dejvice district.
  • C. Velké Poříčí
    Velké Poříčí is a municipality and village in the Hradec Králové Region of the Czech Republic, situated near the town of Náchod close to the Polish border.
  • D. Jindřišská
    Jindřišská is a central Prague street known for connecting Wenceslas Square with the historic Jindřišská Tower and serving as a major tram and traffic route in the city center.
  • E. Vltavská
    Vltavská is a Prague Metro station on Line C, located near the Vltava River in the Holešovice area of Prague, Czech Republic.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e51d39d081909bcfafeaaf3d2fcc completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65809da2c8190bb579ef42513b74d completed April 20, 2026, 4:44 p.m.
Created at: April 10, 2026, 1:51 p.m.