Triple

T37116582
Position Surface form Disambiguated ID Type / Status
Subject Mumbai Division E919132 entity
Predicate overseesRoute P119112 FINISHED
Object Mumbai–Pune line (Central Railway section) NE NERFINISHED

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: Mumbai–Pune line (Central Railway section) | Statement: [Mumbai Division, overseesRoute, Mumbai–Pune line (Central Railway section)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: overseesRoute
Context triple: [Mumbai Division, overseesRoute, Mumbai–Pune line (Central Railway section)]
  • A. controlsRoute chosen
    Indicates that one entity has authority over or manages the path, course, or routing taken by another entity.
  • B. routeOf
    Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
  • C. coreRouteOf
    Indicates that one entity serves as the primary or central route associated with another entity (such as a network, service, or system).
  • D. onStandardRouteOf
    Indicates that something lies along or follows the usual, predefined, or officially designated route of another entity.
  • E. route
    Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
  • 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_69f76e9c57148190ba789dd059645bb9 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fba2877b248190a974eb092243c0c4 completed May 6, 2026, 8:20 p.m.
PD Predicate disambiguation batch_69fb8d06a1b48190a937aa410d159dfa completed May 6, 2026, 6:48 p.m.
Created at: May 3, 2026, 4:15 p.m.