Triple

T16234885
Position Surface form Disambiguated ID Type / Status
Subject South East Delhi district E394079 entity
Predicate containsNeighborhood P4813 FINISHED
Object Okhla E204597 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: Okhla | Statement: [South East Delhi district, containsNeighborhood, Okhla]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Okhla
Context triple: [South East Delhi district, containsNeighborhood, Okhla]
  • A. Okhla chosen
    Okhla is a locality in South Delhi, India, known for its industrial areas, residential colonies, and proximity to the Yamuna River.
  • B. Kharela
    Kharela is a rural village located in the Mahoba district of Uttar Pradesh, India.
  • C. Karwi
    Karwi is a town in Uttar Pradesh, India, known primarily as the rail and road gateway to the historic hill fort of Kalinjar.
  • D. Mehsana
    Mehsana is a prominent city in the Indian state of Gujarat, known for its dairy industry, oil and natural gas fields, and historical temples.
  • E. Haldi
    Haldi is the chief war and national god of the ancient Kingdom of Urartu, central to its state religion and royal ideology.
  • 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_69d87f204df88190a8f88923decf9835 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e24559af48819092e4b466778b07e2 completed April 17, 2026, 2:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a000ed71f488190bcdc2dcc74e5c5d3 completed May 10, 2026, 4:51 a.m.
Created at: April 10, 2026, 5:04 a.m.