Triple

T12042005
Position Surface form Disambiguated ID Type / Status
Subject Nepomuk E286683 entity
Predicate hasTwinTown P919 FINISHED
Object Kiskunfélegyháza E418702 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: Kiskunfélegyháza | Statement: [Nepomuk, hasTwinTown, Kiskunfélegyháza]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kiskunfélegyháza
Context triple: [Nepomuk, hasTwinTown, Kiskunfélegyháza]
  • A. Kiskunfélegyháza chosen
    Kiskunfélegyháza is a town in central Hungary known for its historical market-town character and location in the Great Hungarian Plain.
  • B. Kiskőrös
    Kiskőrös is a small town in southern Hungary known as the birthplace of the national poet Sándor Petőfi and for its wine-producing region.
  • C. Kisújszállás
    Kisújszállás is a small town in eastern Hungary known for its agricultural surroundings and location on the Great Hungarian Plain.
  • D. Nagykőrös
    Nagykőrös is a historic town in central Hungary known for its agricultural traditions and small-town character.
  • E. Füzesabony
    Füzesabony is a small town in northeastern Hungary known as a regional railway junction and gateway to the Bükk and Mátra regions.
  • 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_69d6ab4780948190bdb9f7620c2ac27e completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9040d13108190bd1a969fa62aae5a completed April 10, 2026, 2:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69f49da728ec819080c349fd8d0ed62c completed May 1, 2026, 12:33 p.m.
Created at: April 8, 2026, 9:47 p.m.