Triple

T19025395
Position Surface form Disambiguated ID Type / Status
Subject Firozpur railway division E465595 entity
Predicate hasMajorTrafficType P59443 FINISHED
Object Passenger traffic 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: Passenger traffic | Statement: [Firozpur railway division, hasMajorTrafficType, Passenger traffic]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMajorTrafficType
Context triple: [Firozpur railway division, hasMajorTrafficType, Passenger traffic]
  • A. hasMajorRouteType
    Indicates that an entity is associated with a primary classification of transportation route (such as highway, rail line, or other major route type).
  • B. hasPrimaryTrafficType chosen
    Indicates that an entity is associated with a main or predominant type of traffic it handles or is designed for.
  • C. majorTrafficType
    Indicates the primary kind of traffic or flow that predominantly characterizes a given route, segment, or transportation context.
  • D. hasTrafficMode
    Indicates the mode or type of traffic associated with or applicable to an entity (e.g., pedestrian, vehicular, public transit).
  • E. hasTrafficFeature
    Indicates that an entity possesses or is associated with a specific traffic-related characteristic, element, or infrastructure feature.
  • 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_69d8dd025c188190a1d81f5b4ec7e2c6 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d6e271848190b67ad08af35b6796 completed April 20, 2026, 7:33 a.m.
PD Predicate disambiguation batch_69e4a2fd80c081908237317a3a883e1c completed April 19, 2026, 9:40 a.m.
Created at: April 10, 2026, 12:02 p.m.