Triple

T25539853
Position Surface form Disambiguated ID Type / Status
Subject Asansol railway division E640146 entity
Predicate hasMajorCommodityTraffic P32692 FINISHED
Object coal 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: coal | Statement: [Asansol railway division, hasMajorCommodityTraffic, coal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMajorCommodityTraffic
Context triple: [Asansol railway division, hasMajorCommodityTraffic, coal]
  • A. handlesCargoTraffic
    Indicates that an entity is responsible for managing or processing the movement of cargo traffic.
  • B. hasCargoTrafficType chosen
    Indicates that an entity is associated with a specific type or category of cargo traffic it handles or supports.
  • C. hasPassengerTrafficFrom
    Indicates that an entity receives or handles passenger traffic originating from another entity.
  • D. hasCargoTrafficLevel
    Indicates the intensity or volume of cargo-related traffic associated with an entity, such as a route, location, or transport facility.
  • E. hasMajorTransportInfrastructure
    Indicates that a location possesses significant transportation facilities or networks, such as major roads, railways, ports, or airports, that support substantial movement of people or goods.
  • 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_69e75dbfff7081909b0aa779d48321d2 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f73223675481908c1bc3208c0f5284 completed May 3, 2026, 11:31 a.m.
PD Predicate disambiguation batch_69f7317690108190b3aae2cd2e1d069e completed May 3, 2026, 11:28 a.m.
Created at: April 21, 2026, 3:25 p.m.