Triple
T35787140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beijing food supply system |
E1034594
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | food distribution network |
C29604
|
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: food distribution network Context triple: [Beijing food supply system, instanceOf, food distribution network]
-
A.
food distribution program
A food distribution program is an organized initiative that procures, manages, and delivers food to individuals or communities in need to improve food security and reduce hunger.
-
B.
logistics network
A logistics network is an interconnected system of facilities, transportation modes, and information flows designed to efficiently move goods from origin to destination while optimizing cost, time, and service quality.
-
C.
storage and distribution system
chosen
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.
-
D.
wholesale food market
A wholesale food market is a large-scale marketplace where food products are bought and sold in bulk, typically between producers, distributors, and retailers rather than directly to consumers.
-
E.
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.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.