Triple

T11840465
Position Surface form Disambiguated ID Type / Status
Subject Itarsi E281636 entity
Predicate connectsRailRoutes P24517 FINISHED
Object north India LITERAL 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: north India | Statement: [Itarsi, connectsRailRoutes, north India]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsRailRoutes
Context triple: [Itarsi, connectsRailRoutes, north India]
  • A. hasRailRoute
    Indicates that there exists a rail-based transportation route or connection between the related entities.
  • B. countryRailConnection
    Indicates that there is a railway connection or service linking two countries.
  • C. coordinatesRailTrafficWith
    Indicates that one entity organizes and synchronizes rail operations or movements with another entity to ensure coordinated train traffic.
  • D. railroadNetwork chosen
    Indicates a relationship where locations are connected as part of the same system of railway lines and infrastructure used for train transport.
  • E. railTracks
    Indicates that one entity consists of, includes, or is associated with rail tracks used for guiding trains or rail vehicles.
  • F. None of above.

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_69d6ab276f8c8190b1966a0ef11349ac completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a658f918819092c2db05fe2ab0ce completed April 10, 2026, 7:27 a.m.
PD Predicate disambiguation batch_69d8a254a57481908a1e6ad97919c416 completed April 10, 2026, 7:10 a.m.
Created at: April 8, 2026, 9:43 p.m.