Triple
T13242112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Penn |
E315304
|
entity |
| Predicate | shipmentType |
P94644
|
FINISHED |
| Object | less-than-truckload shipments |
—
|
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: less-than-truckload shipments | Statement: [New Penn, shipmentType, less-than-truckload shipments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipmentType Context triple: [New Penn, shipmentType, less-than-truckload shipments]
-
A.
freightType
chosen
Indicates the category or mode of freight associated with a shipment or transport activity.
-
B.
typeOfHaulage
Indicates the kind or category of haulage service or transport operation associated with an entity.
-
C.
shippingFunction
Indicates the method or process by which goods are transported or delivered from a sender to a recipient.
-
D.
shippingAccess
Indicates that one entity has the ability or permission to ship items to or on behalf of another entity.
-
E.
shippingLaneFor
Indicates that one entity serves as a designated shipping lane or route used for the transportation or navigation of another entity (such as ships or cargo).
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d59e84c8190a9e547d0fe26a5f9 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:23 p.m.