Triple

T22687627
Position Surface form Disambiguated ID Type / Status
Subject Bareilly–Pilibhit–Lalkuan line E560959 entity
Predicate connects P390 FINISHED
Object Pilibhit E213187 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: Pilibhit | Statement: [Bareilly–Pilibhit–Lalkuan line, connects, Pilibhit]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pilibhit
Context triple: [Bareilly–Pilibhit–Lalkuan line, connects, Pilibhit]
  • A. Pilibhit chosen
    Pilibhit is a city in the Rohilkhand region of Uttar Pradesh, India, known for its agricultural economy, historical significance, and proximity to the Pilibhit Tiger Reserve.
  • B. Bijbehara
    Bijbehara is a historic town in the Kashmir Valley of Jammu and Kashmir, India, known for its apple orchards and scenic location along the Jhelum River.
  • C. Tikamgarh
    Tikamgarh is a town and administrative center in central India, known for its historical forts and temples in the state of Madhya Pradesh.
  • D. Ratangarh
    Ratangarh is a town in the Churu district of Rajasthan, India, known for its historic havelis and traditional Rajasthani architecture.
  • E. Bhind
    Bhind is a city in the northern part of the Indian state of Madhya Pradesh, known as an administrative and commercial center of the region.
  • 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_69e2454d71b48190a1f80af9f82b6fcf completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f178983fc8819080aa00e45ff77952 completed April 29, 2026, 3:18 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0b73f90304819084b6c4c944cbf504 completed May 18, 2026, 8:18 p.m.
Created at: April 17, 2026, 3:13 p.m.