Triple
T13526931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota dealer network |
E323036
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | distribution network |
C14644
|
CONCEPT FINISHED |
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: distribution network Context triple: [Toyota dealer network, instanceOf, distribution network]
-
A.
global distribution system provider
A global distribution system provider is a company that operates a computerized network enabling transactions between travel service suppliers (such as airlines, hotels, and car rental companies) and travel agencies or end customers worldwide.
-
B.
storage and distribution system
A storage and distribution system is an integrated arrangement of facilities, equipment, and processes designed to efficiently receive, store, manage, and deliver goods or resources to their intended destinations.
-
C.
manufacturing network
A manufacturing network is an interconnected system of facilities, suppliers, technologies, and logistics that collaboratively plan, produce, and distribute goods across multiple locations.
-
D.
franchise network
chosen
A franchise network is a structured system in which a central franchisor licenses its brand, business model, and support services to multiple independent franchisees operating under unified standards across different locations.
-
E.
telecommunications network
A telecommunications network is a system of interconnected nodes, transmission media, and protocols that enables the exchange of voice, data, and multimedia information between users and devices over distance.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:44 p.m.