Triple
T3704145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian railway network |
E80849
|
entity |
| Predicate | freightUsage |
P28699
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
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: yes | Statement: [Belgian railway network, freightUsage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freightUsage Context triple: [Belgian railway network, freightUsage, yes]
-
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.
logisticsFeature
chosen
Indicates that something possesses a characteristic, capability, or function specifically related to logistics operations or processes.
-
C.
isOnFreightRoute
Indicates that something lies along or is included within a designated freight transportation route used for moving goods.
-
D.
isKeyFreightRoute
Indicates that a transportation route serves as a primary or strategically important corridor for moving freight.
-
E.
hasCargoServices
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
- 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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc54aaac88190b775dba2513b6d4a |
completed | March 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69adb84eeca48190bb4de637e9f0e27a |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:33 p.m.