Triple

T32054214
Position Surface form Disambiguated ID Type / Status
Subject 2006 Mumbai train bombings E818570 entity
Predicate notableStationAffected P154579 FINISHED
Object Bandra E269503 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: Bandra | Statement: [2006 Mumbai train bombings, notableStationAffected, Bandra]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableStationAffected
Context triple: [2006 Mumbai train bombings, notableStationAffected, Bandra]
  • A. trainStationAffected chosen
    Indicates that a train station is impacted or influenced by a particular event, condition, or action.
  • B. causedTransportDisruption
    Indicates that one entity was the cause of a disruption or interruption to the normal operation of a transport system or service.
  • C. servesAsThroughStationFor
    Indicates that a station functions as an intermediate (through) stop for a particular service, route, or journey rather than as its starting or ending point.
  • D. hasNotableStation
    Indicates that an entity possesses or is associated with a station that is considered notable or significant in some context.
  • E. cityTransportOperatorAffected
    Indicates that a city transport operator is impacted or influenced by a particular event, condition, or circumstance.
  • F. None of above.

Provenance (4 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_69f348fdacec8190b9f74375ca3b2094 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_6a037c894b488190bcbec2eccaff4a01 completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2ed503b36c81908b28e6b3deff6a59 completed June 14, 2026, 4:21 p.m.
PD Predicate disambiguation batch_6a0379eaa540819095a1c5d9f3513f9b completed May 12, 2026, 7:05 p.m.
Created at: May 1, 2026, 12:21 a.m.