Triple

T14059750
Position Surface form Disambiguated ID Type / Status
Subject Heves County E338311 entity
Predicate contains P35 FINISHED
Object Mátrafüred E338313 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: Mátrafüred | Statement: [Heves County, contains, Mátrafüred]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mátrafüred
Context triple: [Heves County, contains, Mátrafüred]
  • A. Mátrafüred chosen
    Mátrafüred is a small resort village in northern Hungary known as a popular gateway for hiking and nature tourism in the Mátra Mountains.
  • B. Parádfürdő
    Parádfürdő is a spa village in northern Hungary known for its mineral springs and scenic location within the Mátra mountain region.
  • C. Mátraháza
    Mátraháza is a small mountain resort village in northern Hungary, known for its scenic location in the Mátra range and its hiking and wellness tourism.
  • D. Felvidék
    Felvidék is a historical term, mainly used in Hungarian contexts, referring to the northern upland regions of the former Kingdom of Hungary, much of which lies in present-day Slovakia.
  • E. Tiszafüred
    Tiszafüred is a Hungarian town on the shores of Lake Tisza, known as a regional tourism and recreation center in the Northern Great Plain.
  • 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_69d81c67ba6c819091935650dfb3b895 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5686f51c81908c33143ecbaae83d completed April 14, 2026, 3 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcb662c37c8190a629278a97060080 completed May 7, 2026, 3:57 p.m.
Created at: April 9, 2026, 10:21 p.m.