Triple

T12042151
Position Surface form Disambiguated ID Type / Status
Subject Tachov District E286688 entity
Predicate administrativeCenter P1474 FINISHED
Object Tachov E286678 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: Tachov | Statement: [Tachov District, administrativeCenter, Tachov]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tachov
Context triple: [Tachov District, administrativeCenter, Tachov]
  • A. Tachov chosen
    Tachov is a town in western Czechia that serves as an administrative center and local hub within the Plzeň Region.
  • B. Tuchów
    Tuchów is a small historic town in southern Poland known for its religious pilgrimage site and traditional regional culture.
  • C. Turbacz
    Turbacz is the highest peak of Poland’s Gorce Mountains, known for its extensive forested slopes and panoramic views, and as a popular destination for hikers.
  • D. Tuchan
    Tuchan is a small commune in southern France’s Aude department, known for its wine production and scenic location in the Corbières hills.
  • E. Olecko
    Olecko is a small town in northeastern Poland known for its lakeside setting and location within the historic region of Masuria.
  • 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_69d6ab4780948190bdb9f7620c2ac27e completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9040d13108190bd1a969fa62aae5a completed April 10, 2026, 2:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69f5f649dbf081908e76c45e362217c1 completed May 2, 2026, 1:04 p.m.
Created at: April 8, 2026, 9:47 p.m.