Triple

T4008411
Position Surface form Disambiguated ID Type / Status
Subject Südkreuz station E89582 entity
Predicate railwayCode P18202 FINISHED
Object BKS 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: BKS | Statement: [Südkreuz station, railwayCode, BKS]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railwayCode
Context triple: [Südkreuz station, railwayCode, BKS]
  • A. railroadCodeFor chosen
    Indicates that a specific railroad code is assigned to or used to identify a particular railroad entity.
  • B. railwayName
    Indicates the name assigned to a specific railway or railway line in the relationship.
  • C. railwayLineNumber
    Indicates the identifying number assigned to a specific railway line within a rail network.
  • D. railwayCompany
    Indicates that one entity is a railway company that owns, operates, or manages railway services or infrastructure in relation to another entity.
  • E. railServiceType
    Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
  • 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_69aed9585e788190bec2d39deba3750f completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefaec08dc8190a341809059554f84 completed March 9, 2026, 4:53 p.m.
PD Predicate disambiguation batch_69aef8fa6fec81909b1190ecbba61410 completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:34 p.m.