Triple
T30071244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British railway industry |
E764186
|
entity |
| Predicate | includesFreightOperators |
P34619
|
FINISHED |
| Object | DB Cargo UK |
—
|
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: DB Cargo UK | Statement: [British railway industry, includesFreightOperators, DB Cargo UK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFreightOperators Context triple: [British railway industry, includesFreightOperators, DB Cargo UK]
-
A.
freightOperatorOnCorridor
Indicates that a particular freight operator provides services or operates along a specified transport corridor.
-
B.
shipOperator
Indicates the entity that is responsible for operating, managing, or running a ship.
-
C.
primaryCargoOperator
Indicates that an entity serves as the main organization responsible for operating or managing the cargo-related activities of another entity.
-
D.
transportOperator
chosen
Indicates that an entity is responsible for operating or managing the transportation of people or goods between locations.
-
E.
freightConnections
Indicates the existence or characteristics of transportation links used to move freight or cargo between locations or entities.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
Created at: April 29, 2026, 7 p.m.