Triple
T17895119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian broad-gauge network |
E447412
|
entity |
| Predicate | typicalFreight |
P94644
|
FINISHED |
| Object | bulk commodities |
—
|
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: bulk commodities | Statement: [Russian broad-gauge network, typicalFreight, bulk commodities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFreight Context triple: [Russian broad-gauge network, typicalFreight, bulk commodities]
-
A.
freightType
chosen
Indicates the category or mode of freight associated with a shipment or transport activity.
-
B.
freightTraffic
Indicates the movement or volume of goods and cargo being transported, typically via commercial transport networks such as rail, road, sea, or air.
-
C.
typeOfHaulage
Indicates the kind or category of haulage service or transport operation associated with an entity.
-
D.
typicalOverhead
Indicates the usual or expected amount of additional cost, time, or resource usage associated with performing an action or maintaining a relationship.
-
E.
typicalReturnCargo
Indicates that something is the kind of cargo that is usually carried back on a return trip or journey.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d7eb4f48190951e26975b57873b |
completed | April 19, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.