Triple

T902256
Position Surface form Disambiguated ID Type / Status
Subject Delhi Metro E19472 entity
Predicate serves P98 FINISHED
Object Gurugram E78440 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: Gurugram | Statement: [Delhi Metro, serves, Gurugram]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gurugram
Context triple: [Delhi Metro, serves, Gurugram]
  • A. Gurugram chosen
    Gurugram is a major financial and technology hub in the Indian state of Haryana, known for its modern skyline, multinational corporate offices, and proximity to New Delhi.
  • B. Noida
    Noida is a major planned city and technology hub in the National Capital Region near Delhi, known for its modern infrastructure, IT parks, and residential developments.
  • C. Faridabad
    Faridabad is a major industrial city in northern India known for its manufacturing sector and its location within the National Capital Region near New Delhi.
  • D. Delhi
    Delhi is a major metropolitan region and the capital territory of India, known for its political significance, rich history, and diverse culture.
  • E. Ghaziabad
    Ghaziabad is a major industrial and residential city in the Indian state of Uttar Pradesh, forming part of the National Capital Region near Delhi.
  • 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_69a4939e889c8190ac148b3ac1a7f90b completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ad56f4c08190a7a5091ff0eb3209 completed March 1, 2026, 9:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad3ffcca648190b73d39b92dafe0fe completed March 8, 2026, 9:23 a.m.
Created at: March 1, 2026, 7:39 p.m.