Triple
T35379828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NMBS Logistics |
E1022613
|
entity |
| Predicate | operatedInRegulatoryContext |
P34837
|
FINISHED |
| Object | European rail liberalisation |
—
|
NE NERFINISHED |
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: European rail liberalisation | Statement: [NMBS Logistics, operatedInRegulatoryContext, European rail liberalisation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInRegulatoryContext Context triple: [NMBS Logistics, operatedInRegulatoryContext, European rail liberalisation]
-
A.
operatedWithinRegulatoryBody
Indicates that an entity carried out its activities under the authority, oversight, or framework of a specific regulatory body.
-
B.
regulatedIn
Indicates that one entity’s activity, expression, or occurrence is controlled, influenced, or modulated by another entity within a specific context or system.
-
C.
subjectToRegulation
chosen
Indicates that an entity is governed, constrained, or controlled by a specific rule, law, or regulatory framework.
-
D.
hasRegulatoryUse
Indicates that something is used, applied, or referenced within a regulatory, legal, or compliance context.
-
E.
hasRegulatedBy
Indicates that one entity is subject to control, governance, or rules imposed by another entity.
- F. None of above.
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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a013b78bde881909a082beced4e0157 |
completed | May 11, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_6a013acf45508190a999b208066072bd |
completed | May 11, 2026, 2:11 a.m. |
Created at: May 3, 2026, 4:03 p.m.