Triple

T18853867
Position Surface form Disambiguated ID Type / Status
Subject Elizabeth Bridge E461118 entity
Predicate hasLocalName P6353 FINISHED
Object Erzsébet híd 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: Erzsébet híd | Statement: [Elizabeth Bridge, hasLocalName, Erzsébet híd]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Erzsébet híd
Context triple: [Elizabeth Bridge, hasLocalName, Erzsébet híd]
  • A. Erzsébet híd chosen
    Erzsébet híd is a prominent suspension bridge in Budapest that spans the Danube River, connecting the city’s Buda and Pest sides.
  • B. Belvárosi Bridge
    Belvárosi Bridge is a prominent road and tram bridge over the Tisza River in Szeged, Hungary, serving as one of the city’s key architectural and transport landmarks.
  • C. Széchenyi lánchíd
    Széchenyi lánchíd is a historic 19th-century suspension bridge spanning the Danube River in Budapest, Hungary, and is one of the city’s most iconic landmarks.
  • D. Margit Bridge
    Margit Bridge is a historic arch bridge in Budapest spanning the Danube River and linking the city’s Buda and Pest sides.
  • E. Megyeri Bridge
    Megyeri Bridge is a modern cable-stayed bridge over the Danube River in Budapest, Hungary, serving as a key northern bypass for the city’s ring road system.
  • 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_69d8dcfa11e4819090ab1ef5bdcd2b2e completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c05b4d8881909af0238f451b0e31 completed April 20, 2026, 5:57 a.m.
Created at: April 10, 2026, 11:56 a.m.