Triple

T3668400
Position Surface form Disambiguated ID Type / Status
Subject Sukkur E77817 entity
Predicate locatedNear P294 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: [Sukkur, locatedNear, Rohri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rohri
Context triple: [Sukkur, locatedNear, 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. Kathiawar
    Kathiawar is a peninsula in western India, in present-day Gujarat, historically known for its princely states and coastal trade centers.
  • C. Sangrur
    Sangrur is a city in the Indian state of Punjab known as an agricultural and administrative center within the Malwa region.
  • D. Salbai
    Salbai is a historical location in India known primarily as the site where the 1782 Treaty of Salbai was concluded between the British East India Company and the Maratha Empire.
  • E. Karimabad
    Karimabad is a neighborhood in Karachi, Pakistan, known for its bustling markets and central urban location within the city.
  • 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_69ad85e083008190b2e1b7085fe500bd completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc42997d88190bc765559bd7645fc completed March 8, 2026, 6:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4e4e0abd08190895897c62a7a5243 completed March 14, 2026, 4:32 a.m.
Created at: March 8, 2026, 3:25 p.m.