Triple

T20862766
Position Surface form Disambiguated ID Type / Status
Subject Géza E513662 entity
Predicate burialPlace P196 FINISHED
Object Fehérvár (probable) 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: Fehérvár (probable) | Statement: [Géza, burialPlace, Fehérvár (probable)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fehérvár (probable)
Context triple: [Géza, burialPlace, Fehérvár (probable)]
  • A. Fehérvár chosen
    Fehérvár is a historic Hungarian town, later known as Székesfehérvár, that served as an early royal and administrative center of the Kingdom of Hungary.
  • B. Ferencváros
    Ferencváros is a historic district of Budapest, Hungary, known for its vibrant urban life, cultural venues, and mix of traditional and modern architecture.
  • C. Szepes
    Szepes is a historic region in present-day northeastern Slovakia, known for its medieval towns, castles, and mixed Slovak, German, and Hungarian cultural heritage.
  • D. Kisvárda FC
    Kisvárda FC is a Hungarian professional football club based in the town of Kisvárda that competes in the country’s top divisions.
  • E. Kaposvári Rákóczi FC
    Kaposvári Rákóczi FC is a Hungarian professional football club based in the city of Kaposvár, known for competing in the national league system and developing local talent.
  • 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_69e0b4f5b01081909452f654d2fc3f50 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c45d2ec4819098abbb901b9fcd87 completed April 21, 2026, 12:27 a.m.
Created at: April 16, 2026, 12:44 p.m.