Triple
T15318555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RF&P Subdivision |
E366225
|
entity |
| Predicate | freightFunction |
P28699
|
FINISHED |
| Object | intermodal freight traffic |
—
|
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: intermodal freight traffic | Statement: [RF&P Subdivision, freightFunction, intermodal freight traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freightFunction Context triple: [RF&P Subdivision, freightFunction, intermodal freight traffic]
-
A.
freightType
Indicates the category or mode of freight associated with a shipment or transport activity.
-
B.
freightConnections
Indicates the existence or characteristics of transportation links used to move freight or cargo between locations or entities.
-
C.
logisticsFeature
chosen
Indicates that something possesses a characteristic, capability, or function specifically related to logistics operations or processes.
-
D.
isOnFreightRoute
Indicates that something lies along or is included within a designated freight transportation route used for moving goods.
-
E.
shippingFunction
Indicates the method or process by which goods are transported or delivered from a sender to a recipient.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd356b881908f054b64eee6a371 |
completed | April 16, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.