Triple

T14643549
Position Surface form Disambiguated ID Type / Status
Subject Parádfürdő E343785 entity
Predicate locatedNear P294 FINISHED
Object Recsk E1113224 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: Recsk | Statement: [Parádfürdő, locatedNear, Recsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Recsk
Context triple: [Parádfürdő, locatedNear, Recsk]
  • A. Recsk chosen
    Recsk is a village in northern Hungary known historically for its former political prison and labor camp during the communist era.
  • B. Nagykőrös
    Nagykőrös is a historic town in central Hungary known for its agricultural traditions and small-town character.
  • C. Bicske
    Bicske is a small town in central Hungary known for its historical significance and location along major transportation routes west of Budapest.
  • D. Balvanyos
    Balvanyos is a Romanian mountain resort area known for its natural mineral springs, spa facilities, and scenic surroundings in the Eastern Carpathians.
  • E. Derecske
    Derecske is a small town in eastern Hungary located within Hajdú-Bihar County, known for its agricultural surroundings and local rural character.
  • 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_69d822e1a2cc81908e5bb93cf61ce3cc completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb4e80aa48190884bab800f357106 completed April 14, 2026, 9:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe9dba87c481908084c3cba5df3fcd completed May 9, 2026, 2:36 a.m.
Created at: April 10, 2026, 1:26 a.m.