Triple
T26677686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highway 402 (Ontario) |
E672507
|
entity |
| Predicate | freightImportance |
P161111
|
FINISHED |
| Object | major truck route |
—
|
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: major truck route | Statement: [Highway 402 (Ontario), freightImportance, major truck route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freightImportance Context triple: [Highway 402 (Ontario), freightImportance, major truck route]
-
A.
shippingLaneImportance
Indicates the degree to which a particular shipping lane is considered significant or critical relative to other possible routes.
-
B.
isFreightIntensive
Indicates that an activity, process, or operation involves a high volume or intensity of freight movement or transportation.
-
C.
freightType
Indicates the category or mode of freight associated with a shipment or transport activity.
-
D.
freightTraffic
Indicates the movement or volume of goods and cargo being transported, typically via commercial transport networks such as rail, road, sea, or air.
-
E.
portImportance
Indicates the relative significance or strategic value of a port within a given context (such as trade, logistics, or transportation networks).
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f617053a8081908c4b413a38c84e41 |
completed | May 2, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 3:17 a.m.