Triple

T20830088
Position Surface form Disambiguated ID Type / Status
Subject Nelahozeves E512804 entity
Predicate hasOfficialName P66 FINISHED
Object Nelahozeves 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: Nelahozeves | Statement: [Nelahozeves, hasOfficialName, Nelahozeves]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nelahozeves
Context triple: [Nelahozeves, hasOfficialName, Nelahozeves]
  • A. Nelahozeves chosen
    Nelahozeves is a historic village in the Czech Republic best known as the birthplace of composer Antonín Dvořák.
  • B. Sézenove
    Sézenove is a small village in the municipality of Bernex in the canton of Geneva, Switzerland.
  • C. Háje
    Háje is a Prague Metro station serving as the southern terminus of Line C in the Háje district of the city.
  • D. Puruhá
    The Puruhá are an Indigenous people of the central Andean region of Ecuador, known for their rich pre-Inca cultural heritage, traditional agriculture, and enduring Kichwa-based language and customs.
  • E. Baníkov
    Baníkov is a prominent peak in Slovakia’s Western Tatras, popular with hikers for its rugged ridges and panoramic alpine views.
  • 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_69e0b4ce39108190a6e8e5df4f1c8dc5 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c32177188190ad67572cb3b5db74 completed April 21, 2026, 12:21 a.m.
Created at: April 16, 2026, 12:42 p.m.