Triple
T38223082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German ICE |
E1012064
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | brand of train service |
C14083
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: brand of train service Context triple: [German ICE, instanceOf, brand of train service]
-
A.
high-speed rail service brand
chosen
A high-speed rail service brand is a distinct identity and marketing concept that represents a specific provider’s fast, long-distance passenger train services, encompassing its name, visual design, service standards, and customer experience.
-
B.
regional rail service brand
A regional rail service brand is a distinct identity used to market and organize passenger train services within a specific geographic area, encompassing naming, visual design, and service characteristics.
-
C.
urban rail service brand
An urban rail service brand is the distinctive identity, including name, visual design, and perceived qualities, that represents and differentiates a city's rail transit services in the minds of users and stakeholders.
-
D.
rail freight brand
A rail freight brand is the distinct identity, including name, visual design, reputation, and service promise, that differentiates a company providing cargo transportation by rail from its competitors.
-
E.
named train
A named train is a specific passenger rail service distinguished by a unique name, branding, and often a consistent route and schedule.
- F. None of above.
Provenance (1 batch)
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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.