Triple

T22280235
Position Surface form Disambiguated ID Type / Status
Subject Fehérvár E550711 entity
Predicate hasModernName P20950 FINISHED
Object Székesfehérvár 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: Székesfehérvár | Statement: [Fehérvár, hasModernName, Székesfehérvár]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Székesfehérvár
Context triple: [Fehérvár, hasModernName, Székesfehérvár]
  • A. Székesfehérvár chosen
    Székesfehérvár is a historic city in central Hungary that served as a medieval royal seat and coronation site for Hungarian kings.
  • B. Gyulafehérvár
    Gyulafehérvár, known today as Alba Iulia in Romania, is a historic city that served as the political and cultural center of Transylvania for centuries.
  • C. Szekesfehervar
    Szekesfehérvár is a historic city in central Hungary that served as a medieval royal seat and coronation site for Hungarian kings.
  • D. Veszprém
    Veszprém is a historic city in western Hungary known for its medieval castle district and role as a regional cultural and administrative center.
  • E. 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.
  • 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_69e11e44d538819097c6b8f333af3352 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f14eab4f848190b1a8ba70f9fb0581 completed April 29, 2026, 12:19 a.m.
Created at: April 16, 2026, 8:40 p.m.