Triple
T30953226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurobalise |
E788602
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | track-mounted transponder |
C11412
|
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: track-mounted transponder Context triple: [Eurobalise, instanceOf, track-mounted transponder]
-
A.
transponder-based toll system
A transponder-based toll system is an automated electronic toll collection method where vehicles equipped with small radio-frequency devices are detected and charged as they pass through toll points without stopping.
-
B.
satellite tracking system
A satellite tracking system is a coordinated set of hardware and software components that continuously determine, monitor, and predict the position and trajectory of satellites in orbit for communication, navigation, and control purposes.
-
C.
GPS device manufacturer
A GPS device manufacturer is a company that designs, produces, and distributes hardware and software systems that use satellite-based positioning to provide navigation, tracking, and location-based services.
-
D.
ship station identifier
A ship station identifier is a unique code or designation assigned to a specific ship’s radio or communication station to distinguish it from all other maritime stations.
-
E.
intelligent transportation system component
chosen
An intelligent transportation system component is a hardware or software element that collects, processes, or communicates transportation-related data to optimize traffic flow, enhance safety, and improve overall system efficiency.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:53 p.m.