Triple

T26400792
Position Surface form Disambiguated ID Type / Status
Subject Tatanagar electric loco shed E663690 entity
Predicate locomotiveTypeHandled P160504 FINISHED
Object electric locomotives 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: electric locomotives | Statement: [Tatanagar electric loco shed, locomotiveTypeHandled, electric locomotives]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locomotiveTypeHandled
Context triple: [Tatanagar electric loco shed, locomotiveTypeHandled, electric locomotives]
  • A. locomotiveTypeContext
    Indicates the contextual relationship specifying the type or classification of a locomotive involved in a given situation or usage.
  • B. laterLocomotiveType
    Indicates that one locomotive type succeeds or comes after another in time, representing a later development or version in locomotive design.
  • C. typicalLocomotiveClass
    Indicates that one locomotive class is the standard or most commonly used class for a given context, operator, or service.
  • D. primaryLocomotiveType
    Indicates the main method or mechanism by which an entity typically moves or travels.
  • E. hasLocomotive
    Indicates that one entity possesses or is equipped with a locomotive as part of its composition or operation.
  • F. None of above. chosen

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_69ee883823988190b418b111be28a44a completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f610f38dc08190b2de9cc09f948fe7 completed May 2, 2026, 2:57 p.m.
PD Predicate disambiguation batch_69f5f800fa9c8190aab0962669fde8ac completed May 2, 2026, 1:11 p.m.
PDg Predicate description generation batch_69f6018ceb1c8190a6a5f84071659a96 completed May 2, 2026, 1:52 p.m.
Created at: April 26, 2026, 11:31 p.m.