Triple
T27171203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Railway Package |
E682913
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European Union railway directive package |
C6352
|
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: European Union railway directive package Context triple: [First Railway Package, instanceOf, European Union railway directive package]
-
A.
European transport agreement
A European transport agreement is a formal, often multilateral, accord between European states that harmonizes rules, standards, and procedures for cross-border transportation of goods and passengers to ensure safety, efficiency, and legal consistency.
-
B.
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.
-
C.
European Union regulation
chosen
A European Union regulation is a binding legislative act that applies directly and uniformly in all EU member states without needing national implementing measures, establishing common rules and standards across the Union.
-
D.
international railway
An international railway is a rail transport system or route that connects and facilitates the movement of passengers and freight between two or more countries across their national borders.
-
E.
railway policy implementation
Railway policy implementation is the process of translating rail-related laws, regulations, and strategic plans into concrete operational actions, projects, and standards across the railway system.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:23 a.m.