Triple

T5913694
Position Surface form Disambiguated ID Type / Status
Subject Catholic Church in Hungary E131524 entity
Predicate headquartersLocation P62 FINISHED
Object Esztergom E175407 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: Esztergom | Statement: [Catholic Church in Hungary, headquartersLocation, Esztergom]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Esztergom
Context triple: [Catholic Church in Hungary, headquartersLocation, Esztergom]
  • A. Esztergom chosen
    Esztergom is a historic Hungarian city on the Danube River that served as an early royal capital and remains a major religious and cultural center.
  • B. Gödöllő
    Gödöllő is a Hungarian town near Budapest best known for its historic Royal Palace, one of the largest Baroque palaces in Hungary.
  • C. Budavár
    Budavár is the historic Buda Castle quarter of Budapest, known for its medieval streets, royal palace complex, and panoramic views over the Danube.
  • D. Budaörs
    Budaörs is a suburban town near Budapest in Hungary, known for its rapid post-communist development and role as a commercial and residential hub.
  • E. Székesfehérvár
    Székesfehérvár is a historic city in central Hungary that served as a medieval royal seat and coronation site for Hungarian kings.
  • 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_69c008593a44819081a07ae0efe6c574 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c037b85c7481908bc9da9d38e02d2b completed March 22, 2026, 6:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69c16e882cdc819082b46b9380c430ad completed March 23, 2026, 4:47 p.m.
Created at: March 22, 2026, 3:59 p.m.