Triple
T33319893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Business |
E853108
|
entity |
| Predicate | typicalRouteUsage |
—
|
GENERATED |
| Object | domestic U.S. routes |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRouteUsage Context triple: [United Business, typicalRouteUsage, domestic U.S. routes]
-
A.
usageRoute
Indicates the path, method, or channel through which something is used, applied, or accessed.
-
B.
usedRoutes
chosen
Indicates that an entity has utilized or traveled along specific routes.
-
C.
currentUseOfRoute
Indicates that a particular route is presently being used for a specific purpose, activity, or traffic flow.
-
D.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
E.
onStandardRouteOf
Indicates that something lies along or follows the usual, predefined, or officially designated route of another entity.
- F. None of above.
Provenance (1 batch)
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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:33 a.m.