Triple

T13592009
Position Surface form Disambiguated ID Type / Status
Subject Jewar Airport E324712 entity
Predicate namedAfter P63 FINISHED
Object Jewar town E751727 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: Jewar town | Statement: [Jewar Airport, namedAfter, Jewar town]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jewar town
Context triple: [Jewar Airport, namedAfter, Jewar town]
  • A. Jewar chosen
    Jewar is a town in Uttar Pradesh, India, known for its rapidly developing infrastructure and the upcoming Noida International (Jewar) Airport project.
  • B. Raisinghnagar
    Raisinghnagar is a town and administrative center in the northern Indian state of Rajasthan, known for its agricultural economy within the arid region near the India–Pakistan border.
  • C. Yamunanagar
    Yamunanagar is an industrial city in the Indian state of Haryana, known for its plywood, paper, and metal industries and its proximity to the Yamuna River.
  • D. Rewari
    Rewari is a historic city in the Indian state of Haryana, located near Delhi and known for its brass industry and strategic position in northern India.
  • E. Bhaderwahi
    Bhaderwahi is an Indo-Aryan language spoken primarily in the Bhaderwah region of Jammu and Kashmir, India.
  • 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_69d80769eaf081909d82f44e484d6113 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbb056ce088190a6feb4266633d18b completed April 12, 2026, 2:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69f77f8ffc508190a7bc69745c43a644 completed May 3, 2026, 5:02 p.m.
Created at: April 9, 2026, 9:49 p.m.