Triple
T34051821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | td.Pharma |
E873244
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | temperature-controlled transport product |
C46735
|
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: temperature-controlled transport product Context triple: [td.Pharma, instanceOf, temperature-controlled transport product]
-
A.
transport refrigeration service provider
A transport refrigeration service provider is a business that installs, maintains, and repairs temperature-control systems on vehicles used to transport perishable goods, ensuring reliable cold-chain operations.
-
B.
unpressurized cargo carrier
An unpressurized cargo carrier is a transport container or vehicle section designed to hold goods in an environment exposed to ambient external pressure, typically used for freight that does not require a controlled or pressurized atmosphere.
-
C.
thermal control system
chosen
A thermal control system is a coordinated set of components and mechanisms designed to monitor, regulate, and maintain desired temperature conditions within a physical environment or device.
-
D.
shelf-stable food product
A shelf-stable food product is an edible item that has been processed and packaged to remain safe and palatable for extended periods at room temperature without refrigeration.
-
E.
life-support container
A life-support container is a sealed, controlled-environment unit designed to maintain the necessary conditions (such as air, temperature, pressure, and nutrients) to sustain the life and health of its biological occupants.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:51 a.m.