Triple

T21840544
Position Surface form Disambiguated ID Type / Status
Subject Ladislaus the Posthumous E539240 entity
Predicate placeOfBirth P1 FINISHED
Object Komárom 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: Komárom | Statement: [Ladislaus the Posthumous, placeOfBirth, Komárom]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Komárom
Context triple: [Ladislaus the Posthumous, placeOfBirth, Komárom]
  • A. Komárom chosen
    Komárom is a Hungarian town on the Danube River known for its historic fortifications and its twin-city relationship with Komárno in Slovakia.
  • B. Kazincbarcika
    Kazincbarcika is an industrial town in northeastern Hungary, located in Borsod-Abaúj-Zemplén County.
  • C. Kalocsa
    Kalocsa is a historic town in southern Hungary known as an important Roman Catholic archiepiscopal center and for its traditional paprika production and folk art.
  • D. Komárno
    Komárno is a historic town and river port in southern Slovakia, situated at the confluence of the Danube and Váh rivers on the border with Hungary.
  • E. Dunakeszi
    Dunakeszi is a town in Hungary located just north of Budapest, known as a rapidly growing suburban and commuter settlement along the Danube in Pest 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_69e0c476c3c88190a92d08ebb59a128a completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f0a7ab71e081908e3d3293743e6409 completed April 28, 2026, 12:27 p.m.
Created at: April 16, 2026, 6:55 p.m.