Triple

T34927702
Position Surface form Disambiguated ID Type / Status
Subject Transbay BART network E1007336 entity
Predicate openedYearApprox P132450 FINISHED
Object 1974 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: 1974 | Statement: [Transbay BART network, openedYearApprox, 1974]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: openedYearApprox
Context triple: [Transbay BART network, openedYearApprox, 1974]
  • A. approximateOpeningYear chosen
    Indicates the estimated or roughly determined year in which something (such as a facility, venue, or organization) began operating or opened.
  • B. approximateStartYear
    Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
  • C. estimatedYearOfCreation
    Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
  • D. endYearApprox
    Indicates that the end year of an event, state, or relationship is known only approximately rather than as a precise calendar year.
  • E. releaseApproximateYear
    Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
  • 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_69f76dc3d83881909d5c3c14455cfa2c completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fd592e48cc81909d754cc6c4bd99ae completed May 8, 2026, 3:31 a.m.
PD Predicate disambiguation batch_69fd58b7f9b881909dc099b28d567784 completed May 8, 2026, 3:30 a.m.
Created at: May 3, 2026, 4 p.m.