Triple

T26808281
Position Surface form Disambiguated ID Type / Status
Subject Tianjin Metro Line Z6 E671906 entity
Predicate hasPlannedOpeningStatus P24929 FINISHED
Object not yet in service 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: not yet in service | Statement: [Tianjin Metro Line Z6, hasPlannedOpeningStatus, not yet in service]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPlannedOpeningStatus
Context triple: [Tianjin Metro Line Z6, hasPlannedOpeningStatus, not yet in service]
  • A. plannedOpeningDate
    Indicates the date on which something is scheduled or intended to begin operating or become available.
  • B. hasOpening
    Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
  • C. hasPlanningStatus chosen
    Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
  • D. isOpeningFor
    Indicates that one entity serves as the beginning, introduction, or initial act for another entity, such as an event, performance, or sequence.
  • E. hasOpeningCondition
    Indicates that a relationship or action is subject to a specific initial condition that must be met before it can begin or take effect.
  • 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_69eeb3225a3c8190aaf6746efeded2f3 completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f6b903538481909cffcb6cc1cc0e70 completed May 3, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69f6b626120c819097c9ad04487570d7 completed May 3, 2026, 2:42 a.m.
Created at: April 27, 2026, 4:27 a.m.