Triple

T26362709
Position Surface form Disambiguated ID Type / Status
Subject Victoria tube station E660249 entity
Predicate openingDateDistrictAndCircle P10845 FINISHED
Object 24 December 1868 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: 24 December 1868 | Statement: [Victoria tube station, openingDateDistrictAndCircle, 24 December 1868]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: openingDateDistrictAndCircle
Context triple: [Victoria tube station, openingDateDistrictAndCircle, 24 December 1868]
  • A. openedOnDistrictAndCircleLines
    Indicates that something (such as a station or section) was opened specifically on both the District and Circle railway lines.
  • B. expansionOpeningDate
    Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
  • C. officialOpeningDate chosen
    Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
  • D. openingDateLineB
    Indicates the date on which line B is officially opened or begins operation.
  • E. openingDateAsThirdSectorLine
    Indicates the date on which a railway line was opened specifically as a third-sector (joint public–private) line.
  • 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_69ee8126d52c8190bc0b34337c2c9aa8 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f612607c388190ab61d1ac7d18e08d completed May 2, 2026, 3:04 p.m.
PD Predicate disambiguation batch_69f611a9272881909093360472be832c completed May 2, 2026, 3 p.m.
Created at: April 26, 2026, 10:52 p.m.