Triple

T19078813
Position Surface form Disambiguated ID Type / Status
Subject Maharashtra Metro Rail Corporation Limited E466970 entity
Predicate roleInNagpurMetro P29465 FINISHED
Object implementing agency 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: implementing agency | Statement: [Maharashtra Metro Rail Corporation Limited, roleInNagpurMetro, implementing agency]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInNagpurMetro
Context triple: [Maharashtra Metro Rail Corporation Limited, roleInNagpurMetro, implementing agency]
  • A. hasPublicTransitRole chosen
    Indicates that an entity holds a specific functional role or responsibility within a public transit system.
  • B. partOfTransitSystem
    Indicates that something is a component or segment within a larger transit or transportation system.
  • C. roleInBulletTrain
    Indicates the specific function, position, or responsibility an entity has within the context of a bullet train system or operation.
  • D. servesLocalTrains
    Indicates that a station or facility provides service or stops specifically for local (non-express) train routes.
  • E. roleInNepal
    Indicates that an entity holds or has held a specific role, position, or function within the context of Nepal.
  • 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_69d8dd04f4488190b1121cc53ef2bfd6 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e2e61b60819092d42614f04a087c completed April 20, 2026, 8:25 a.m.
PD Predicate disambiguation batch_69e4b9a604308190a3235184f9f2c056 completed April 19, 2026, 11:16 a.m.
Created at: April 10, 2026, 12:04 p.m.