Triple

T20554095
Position Surface form Disambiguated ID Type / Status
Subject Lajpat Nagar metro station E504670 entity
Predicate pinkLineInterchangeOpening P28725 FINISHED
Object 2018 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: 2018 | Statement: [Lajpat Nagar metro station, pinkLineInterchangeOpening, 2018]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: pinkLineInterchangeOpening
Context triple: [Lajpat Nagar metro station, pinkLineInterchangeOpening, 2018]
  • A. railwayLine
    Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
  • B. railwayLineType
    Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
  • C. lineName chosen
    Indicates the specific name or designation assigned to a particular line (such as a route, path, or service) that distinguishes it from other lines.
  • D. lineConfiguration
    Indicates that the entities participate together in a specific arrangement or pattern along a line.
  • E. lineServed
    Indicates that a particular transportation line (such as a bus, train, or metro line) provides service to or is operated at a given stop, station, or route segment.
  • 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_69e0b4b52c048190952b4d0f430813a3 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a5dbe96c8190a278dfefdb4a5c43 completed April 20, 2026, 10:17 p.m.
PD Predicate disambiguation batch_69e59fe5592c8190bb6122b784496d02 completed April 20, 2026, 3:39 a.m.
Created at: April 16, 2026, 11:38 a.m.