Triple

T22952725
Position Surface form Disambiguated ID Type / Status
Subject Orthodox Church of Kecskemét E570063 entity
Predicate locatedIn P40 FINISHED
Object Kecskemét 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: Kecskemét | Statement: [Orthodox Church of Kecskemét, locatedIn, Kecskemét]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kecskemét
Context triple: [Orthodox Church of Kecskemét, locatedIn, Kecskemét]
  • A. Kecskemét chosen
    Kecskemét is a city in central Hungary known for its Art Nouveau architecture, cultural institutions, and role as an administrative and economic center of the region.
  • B. Békéscsaba
    Békéscsaba is a city in southeastern Hungary known as the administrative center of Békés County and for its cultural and culinary traditions, including its famous sausage.
  • C. Miskolc
    Miskolc is a large industrial and cultural city in northeastern Hungary, known for its steel industry, historic center, and nearby cave baths.
  • D. Szekesfehervar
    Szekesfehérvár is a historic city in central Hungary that served as a medieval royal seat and coronation site for Hungarian kings.
  • E. Kaposvár
    Kaposvár is a city in southwestern Hungary that serves as the administrative and cultural center of Somogy County.
  • 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_69e2459199d08190a8184ee2aa935842 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f181a34c30819099ff4812500a0991 completed April 29, 2026, 3:57 a.m.
Created at: April 17, 2026, 3:46 p.m.