Triple

T4632772
Position Surface form Disambiguated ID Type / Status
Subject Khuldabad E101455 entity
Predicate locatedNear P294 FINISHED
Object Aurangabad city E33321 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: Aurangabad city | Statement: [Khuldabad, locatedNear, Aurangabad city]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aurangabad city
Context triple: [Khuldabad, locatedNear, Aurangabad city]
  • A. Aurangabad chosen
    Aurangabad is a historic city in the Indian state of Maharashtra, known for its rich cultural heritage and proximity to UNESCO World Heritage Sites like the Ajanta and Ellora Caves.
  • B. Aligarh
    Aligarh is a prominent city in northern India known for its lock industry and as the home of Aligarh Muslim University.
  • C. Moradabad
    Moradabad is a major city in northern India known for its brass handicraft industry and is located in the state of Uttar Pradesh.
  • D. Surat
    Surat is a historic port city in the Indian state of Gujarat that became an important center of trade and commerce during the Mughal and early colonial periods.
  • E. Ahmednagar
    Ahmednagar is a historic city in the Indian state of Maharashtra, known for its medieval forts, Mughal-era significance, and role in the Deccan region’s political history.
  • 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_69bd43d2f1c081908cd4b7ec48ecc73d completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd5a342ffc8190a911d0598ed230bb completed March 20, 2026, 2:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69be10330b608190a82e67ceac3b34b7 completed March 21, 2026, 3:27 a.m.
Created at: March 20, 2026, 1:13 p.m.