Triple

T10348363
Position Surface form Disambiguated ID Type / Status
Subject Metro Hidalgo station E243812 entity
Predicate openingDateLine3Section P42368 FINISHED
Object 1970-11-20 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: 1970-11-20 | Statement: [Metro Hidalgo station, openingDateLine3Section, 1970-11-20]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: openingDateLine3Section
Context triple: [Metro Hidalgo station, openingDateLine3Section, 1970-11-20]
  • A. line3OpeningDate chosen
    Indicates the calendar date on which the third line (e.g., a route, service line, or similar system component) was officially opened or began operation.
  • B. openingDateLine16
    Indicates the date on which line 16 was officially opened or began operation.
  • C. lineSectionOpeningDate
    Indicates the date on which a specific section of a line (e.g., a route, track, or corridor) was officially opened for use.
  • D. openingDateLine14
    Indicates the date on which something (such as a service, facility, or record) is opened or begins operation, as specified in line 14 of a form or document.
  • E. openingDate_Line2
    Indicates the secondary or alternative date on which something (such as a facility, service, or event) is opened or becomes operational.
  • 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_69d381b22b8c8190aaed476be5f872a9 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4e945d51881908dd2af6c78344c9b completed April 7, 2026, 11:23 a.m.
PD Predicate disambiguation batch_69d4dfa657f481909cc5cc8fec00ad19 completed April 7, 2026, 10:42 a.m.
Created at: April 6, 2026, 11:56 a.m.