Triple
T8574652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portage, Indiana |
E203016
|
entity |
| Predicate | freightActivity |
P28469
|
FINISHED |
| Object | heavy |
—
|
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: heavy | Statement: [Portage, Indiana, freightActivity, heavy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freightActivity Context triple: [Portage, Indiana, freightActivity, heavy]
-
A.
freightTraffic
chosen
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
Indicates that something possesses a characteristic, capability, or function specifically related to logistics operations or processes.
-
C.
servesAsCargoHubFor
Indicates that one entity functions as a central location or facility for handling, consolidating, and distributing cargo associated with another entity.
-
D.
logistics
Indicates the organization, coordination, and management of how resources, goods, or information are efficiently moved and handled between entities.
-
E.
isOnFreightRoute
Indicates that something lies along or is included within a designated freight transportation route used for moving goods.
- 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_69ca8328ebe481909a8c038fa79959b4 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea947f188190af469babaa73ddf6 |
completed | March 31, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:21 p.m.