Triple

T13627042
Position Surface form Disambiguated ID Type / Status
Subject Faizabad Junction E325610 entity
Predicate connectsTo P845 FINISHED
Object Lucknow E22159 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: Lucknow | Statement: [Faizabad Junction, connectsTo, Lucknow]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lucknow
Context triple: [Faizabad Junction, connectsTo, Lucknow]
  • A. Lucknow chosen
    Lucknow is the capital city of the Indian state of Uttar Pradesh, renowned for its rich cultural heritage, refined Urdu literature, Awadhi cuisine, and elegant Mughal and colonial-era architecture.
  • B. Lucknow
    Lucknow is a small rural community in Bruce County, Ontario, Canada, known for its agricultural character and local festivals.
  • C. Kanpur
    Kanpur is a major industrial city in the northern Indian state of Uttar Pradesh, historically significant as a key site of conflict during the Indian Rebellion of 1857.
  • D. Kanpur Central
    Kanpur Central is one of the busiest and largest railway stations in North India, serving as a major junction and transit hub in the city of Kanpur, Uttar Pradesh.
  • E. Aligarh
    Aligarh is a prominent city in northern India known for its lock industry and as the home of Aligarh Muslim University.
  • 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_69d8076aae28819092cf636190ee5529 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbbe9c72c88190be3d7a3f2e96afbc completed April 12, 2026, 3:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69f77f8ffc508190a7bc69745c43a644 completed May 3, 2026, 5:02 p.m.
Created at: April 9, 2026, 9:51 p.m.