Triple

T5654147
Position Surface form Disambiguated ID Type / Status
Subject Regional-Express E124575 entity
Predicate branding P1500 FINISHED
Object DB Regio E119083 NE 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: DB Regio | Statement: [Regional-Express, branding, DB Regio]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: DB Regio
Context triple: [Regional-Express, branding, DB Regio]
  • A. DB Regio chosen
    DB Regio is a division of Germany’s national railway company that operates most of the country’s regional and local passenger train services.
  • B. DB Regio Bus
    DB Regio Bus is the regional and local bus transport division of Deutsche Bahn, operating extensive bus services across Germany.
  • C. DB Station&Service
    DB Station&Service is a subsidiary of Deutsche Bahn responsible for managing and operating railway stations across Germany.
  • D. ProRail
    ProRail is the Dutch government-owned company responsible for managing and maintaining the national railway infrastructure in the Netherlands.
  • E. InterRegio
    InterRegio is a category of medium- to long-distance passenger trains in several European countries that provides relatively fast regional connections between major cities and regions.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c00825df388190a58742fa9b1aa33d completed March 22, 2026, 3:17 p.m.
NER Named-entity recognition batch_69c022f7efec8190946c925130176d5a completed March 22, 2026, 5:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69c04d97b8dc8190865ff55071954b30 completed March 22, 2026, 8:14 p.m.
Created at: March 22, 2026, 3:42 p.m.