Triple

T8021873
Position Surface form Disambiguated ID Type / Status
Subject Attock E186757 entity
Predicate locatedNear P294 FINISHED
Object Attock Bridge E707740 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: Attock Bridge | Statement: [Attock, locatedNear, Attock Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Attock Bridge
Context triple: [Attock, locatedNear, Attock Bridge]
  • A. Attock Bridge chosen
    Attock Bridge is a historic railway and road bridge spanning the Indus River in Pakistan, linking the provinces of Punjab and Khyber Pakhtunkhwa.
  • B. Neelum Bridge
    Neelum Bridge is a prominent road bridge spanning the Neelum River in Muzaffarabad, Azad Jammu and Kashmir, serving as a key local transportation link and landmark.
  • C. Ayub Bridge
    Ayub Bridge is a historic steel railway bridge spanning the Indus River near Sukkur in Pakistan, known for its distinctive arch design and engineering significance.
  • D. Chenab Rail Bridge
    The Chenab Rail Bridge is a steel and concrete arch railway bridge in Jammu and Kashmir, India, renowned as one of the world’s highest railway bridges.
  • E. Aundh Bridge
    Aundh Bridge is a roadway bridge in Pune, India, that serves as a key connector across the Mula River between the Aundh area and surrounding localities.
  • 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_69ca82ac7fc081909b1398cf025423af completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3e8eab9c81908098e6b17957316c completed March 31, 2026, 3:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc63c6a9208190841ed55b8c6ec73f completed April 1, 2026, 12:16 a.m.
Created at: March 30, 2026, 5:20 p.m.