Triple

T15283481
Position Surface form Disambiguated ID Type / Status
Subject Törökbálint E365332 entity
Predicate roadConnection P385 FINISHED
Object M1 motorway E953979 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: M1 motorway | Statement: [Törökbálint, roadConnection, M1 motorway]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: M1 motorway
Context triple: [Törökbálint, roadConnection, M1 motorway]
  • A. M1 motorway
    The M1 motorway is a major north–south highway in England linking London with key cities in the Midlands and northern England.
  • B. M1 motorway chosen
    The M1 motorway is a major Hungarian highway that connects Budapest with the western regions of the country and continues toward the Austrian border.
  • C. M1 motorway
    The M1 motorway is a major north–south highway in Johannesburg, South Africa, forming part of the city’s primary arterial road network.
  • D. M1 motorway
    The M1 motorway is a major Hungarian highway connecting Budapest with the northwestern city of Győr and the Austrian border, forming part of the main route between Hungary and Western Europe.
  • E. M1 motorway
    The M1 motorway is a major Hungarian highway that connects Budapest with the northwestern border near Austria, forming part of a key international transport corridor.
  • 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_69d85a103d9081908c1ea6c4c73ac8e3 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e00e53c9588190a6cb61ac8805c706 completed April 15, 2026, 10:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a01232149f88190b385fca6a7588d7b completed May 11, 2026, 12:30 a.m.
Created at: April 10, 2026, 3:15 a.m.