Triple
T30181790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail sectorisation era |
E767220
|
entity |
| Predicate | mainFreightSector |
P168521
|
FINISHED |
| Object | Railfreight |
—
|
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: Railfreight | Statement: [British Rail sectorisation era, mainFreightSector, Railfreight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainFreightSector Context triple: [British Rail sectorisation era, mainFreightSector, Railfreight]
-
A.
freightTraffic
Indicates the movement or volume of goods and cargo being transported, typically via commercial transport networks such as rail, road, sea, or air.
-
B.
freightImportance
Indicates the degree to which something is significant, prioritized, or critical in the context of freight transport or logistics.
-
C.
freightType
Indicates the category or mode of freight associated with a shipment or transport activity.
-
D.
freightConnections
Indicates the existence or characteristics of transportation links used to move freight or cargo between locations or entities.
-
E.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
- F. None of above. chosen
Provenance (4 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f42c4708190accbdb72ae9c9816 |
completed | May 2, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:26 p.m.