Triple

T28122032
Position Surface form Disambiguated ID Type / Status
Subject Mayur Vihar Phase 1 metro station E710817 entity
Predicate hasFeederServices P171782 FINISHED
Object yes 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: yes | Statement: [Mayur Vihar Phase 1 metro station, hasFeederServices, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFeederServices
Context triple: [Mayur Vihar Phase 1 metro station, hasFeederServices, yes]
  • A. hasFeederUnion
    Indicates that an entity is associated with or connected to a feeder union, typically one that supplies members, resources, or support to it.
  • B. hasFeederRoutes
    Indicates that one transportation route serves as a feeder, supplying passengers or traffic to another main route.
  • C. hasFeederArea
    Indicates that one entity serves as the source or contributing area that supplies resources, inputs, or influence to another entity.
  • D. hasFeederRelationshipTo
    Indicates that one entity serves as a source of nourishment, resources, or input that sustains, supports, or feeds another entity.
  • E. hasFeederClub
    Indicates that one sports club serves as a feeder organization that develops and supplies players or resources to another, typically higher-level, club.
  • 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_69ef9b73bd288190a21ae3d6aa14f386 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f6a28c7c148190bfc980aad9f678ca completed May 3, 2026, 1:19 a.m.
PD Predicate disambiguation batch_69f69fe1e3c88190830bb2e9f407357e completed May 3, 2026, 1:07 a.m.
PDg Predicate description generation batch_69f6a28b8ea881908733485374771c51 completed May 3, 2026, 1:19 a.m.
Created at: April 27, 2026, 9:17 p.m.