Triple
T33187782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mireo |
E849519
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional train family |
C61010
|
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: regional train family Context triple: [Mireo, instanceOf, regional train family]
-
A.
passenger railcar family
A passenger railcar family is a group of related rail vehicles sharing a common design platform, structural features, and systems, adapted into multiple variants to serve different passenger transport roles and service requirements.
-
B.
multiple-unit train family
chosen
A multiple-unit train family is a group of closely related self-propelled rail vehicles sharing a common design platform, modular components, and performance characteristics, configured in fixed or semi-permanent sets for passenger or freight service.
-
C.
public railway
A public railway is a government- or publicly-owned rail transport system that provides scheduled passenger and/or freight services accessible to the general population, typically operating on standardized tracks and infrastructure.
-
D.
tourist shuttle train
A tourist shuttle train is a small, often open-air rail vehicle designed to transport visitors along scenic or attraction-focused routes, typically at low speeds with frequent stops.
-
E.
regional Train Advise Assist Command
A regional Train Advise Assist Command is a military organizational entity responsible for training, advising, and assisting partner or allied security forces within a specific geographic area to enhance their operational capabilities and self-sufficiency.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:29 a.m.