Triple

T15067044
Position Surface form Disambiguated ID Type / Status
Subject Ayub Bridge E379781 entity
Predicate connects P390 FINISHED
Object Rohri E384157 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: Rohri | Statement: [Ayub Bridge, connects, Rohri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rohri
Context triple: [Ayub Bridge, connects, Rohri]
  • A. Rohri chosen
    Rohri is a historic town in Sindh, Pakistan, situated on the Indus River and known as a key railway and trade junction in the region.
  • B. Sonmiani
    Sonmiani is a coastal town in Pakistan’s Balochistan province known for its beach, fishing community, and strategic location along the Arabian Sea.
  • C. Meerane
    Meerane is a small industrial town in the German state of Saxony that forms part of the wider Leipzig metropolitan region.
  • D. Ganaur
    Ganaur is a town in the northern Indian state of Haryana, known for its agricultural markets and proximity to major transport routes connecting it to Delhi and other regional centers.
  • E. Pehowa
    Pehowa is a historic town in the Indian state of Haryana, known for its ancient temples and significance as a Hindu pilgrimage center.
  • 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_69d85cd7683881908d405c1b5d7b4f7f completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69dedeea750c819082d8823c9ab6c5a2 completed April 15, 2026, 12:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69feb7dd767c8190a129f00303f970bc completed May 9, 2026, 4:28 a.m.
Created at: April 10, 2026, 3:02 a.m.