Triple

T8496694
Position Surface form Disambiguated ID Type / Status
Subject Signature Bridge E201116 entity
Predicate connects P390 FINISHED
Object Wazirabad E220423 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: Wazirabad | Statement: [Signature Bridge, connects, Wazirabad]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wazirabad
Context triple: [Signature Bridge, connects, Wazirabad]
  • A. Wazirabad chosen
    Wazirabad is a city in the Gujranwala District of Punjab, Pakistan, known for its cutlery industry and strategic location near the Chenab River.
  • B. Shujabad
    Shujabad is a city in southern Punjab, Pakistan, known for its agricultural economy and proximity to the regional center of Multan.
  • C. Jamshoro
    Jamshoro is a city in the Sindh province of Pakistan known as an important educational hub, hosting several major universities and research institutions.
  • D. Khuldabad
    Khuldabad is a historic town in Maharashtra, India, renowned as the burial site of the Mughal emperor Aurangzeb and several prominent Sufi saints.
  • E. Amarkot
    Amarkot is an alternative name for Umarkot, a historic town and district in the Sindh province of Pakistan known for its cultural and Mughal-era significance.
  • 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_69ca831ee390819095fae73400bbfafc completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe57f8c508190b3a93ef180db9873 completed March 31, 2026, 3:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce6d120f8c819088a1d9b23b621939 completed April 2, 2026, 1:20 p.m.
Created at: March 30, 2026, 6:13 p.m.