Triple

T14210121
Position Surface form Disambiguated ID Type / Status
Subject Elisabeth Bridge to Buda E352205 entity
Predicate historicConnection P95486 FINISHED
Object historic Buda side LITERAL 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: historic Buda side | Statement: [Elisabeth Bridge to Buda, historicConnection, historic Buda side]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicConnection
Context triple: [Elisabeth Bridge to Buda, historicConnection, historic Buda side]
  • A. historicFor
    Indicates that something holds historical significance or importance specifically in relation to another entity.
  • B. otherHistoricSee
    Indicates that an entity is associated with or linked to another historically significant site, event, or point of interest that can be seen or visited.
  • C. historicSeeOf
    Indicates that a place serves or has served as the principal episcopal seat or central ecclesiastical jurisdiction of a bishop or similar religious authority.
  • D. historicCore chosen
    Indicates that something is part of, located within, or associated with the original historic center or oldest developed area of a place.
  • E. historicActivity
    Indicates that an entity engaged in an activity or event of historical significance in the past.
  • F. None of above.

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_69d8278a06e481908b5d6af0a8afe737 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61fa8d24819092a8ec5d34c1c799 completed April 14, 2026, 3:49 p.m.
PD Predicate disambiguation batch_69de05bcd7d48190a4848d9320404aa6 completed April 14, 2026, 9:15 a.m.
Created at: April 10, 2026, 1:05 a.m.