Triple

T4060846
Position Surface form Disambiguated ID Type / Status
Subject Berlin U-Bahn line U7 E86206 entity
Predicate openedAsIndependentLine P53828 FINISHED
Object 1966 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: 1966 | Statement: [Berlin U-Bahn line U7, openedAsIndependentLine, 1966]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: openedAsIndependentLine
Context triple: [Berlin U-Bahn line U7, openedAsIndependentLine, 1966]
  • A. originalLineOpened
    Indicates that a transportation or service line began its initial operation or was first opened for use.
  • B. openedFirstLine
    Indicates that one entity initiated the opening of something (e.g., a file, document, or interface) before any other entity did, being the first to perform the opening action.
  • C. openedAs
    Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
  • D. openedAsBranchOf
    Indicates that one entity was established and began operating as a branch or subsidiary location of another entity.
  • E. openedAsComplex
    Indicates that one entity was inaugurated or began operation specifically as a multi-part or multi-use complex, rather than as a single standalone facility.
  • 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_69aed93c69208190a4efac0efe3cd69b completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefd0bdea48190805a79515ee92709 completed March 9, 2026, 5:02 p.m.
PD Predicate disambiguation batch_69aef90438908190a005b08ba271eacf completed March 9, 2026, 4:44 p.m.
PDg Predicate description generation batch_69aefd0995188190b1bc8771fe7f423a completed March 9, 2026, 5:02 p.m.
Created at: March 9, 2026, 3:38 p.m.