Triple
T9306259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hub Group |
E223890
|
entity |
| Predicate | offersTechnology |
P87979
|
FINISHED |
| Object | transportation management systems |
—
|
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: transportation management systems | Statement: [Hub Group, offersTechnology, transportation management systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersTechnology Context triple: [Hub Group, offersTechnology, transportation management systems]
-
A.
offeredTechnology
Indicates that one entity has provided or proposed a specific technology to another entity as an option for use, adoption, or consideration.
-
B.
offersFeature
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
C.
offersServiceIn
Indicates that a provider makes a particular service available within a specified location or jurisdiction.
-
D.
offersServiceTo
Indicates that one entity provides or makes a service available for the benefit or use of another entity.
-
E.
offersProduct
Indicates that one entity makes a product available to another entity, typically for sale or use.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd1da7c1e08190af19169f5d806cde |
completed | April 1, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:36 p.m.