Triple
T30969002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalamid–Ras Al Khair phosphate line |
E789038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | phosphate transport corridor |
C2952
|
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: phosphate transport corridor Context triple: [Jalamid–Ras Al Khair phosphate line, instanceOf, phosphate transport corridor]
-
A.
transport corridor
chosen
A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
-
B.
ATP-binding cassette transporter
An ATP-binding cassette transporter is a membrane protein that uses the energy from ATP hydrolysis to move various molecules across cellular membranes, often against their concentration gradients.
-
C.
xenobiotic transporter
A xenobiotic transporter is a membrane protein that mediates the uptake, efflux, or intracellular trafficking of foreign chemical substances (xenobiotics), thereby influencing their absorption, distribution, metabolism, and excretion in an organism.
-
D.
drug transporter
A drug transporter is a membrane protein that facilitates the movement of pharmaceutical compounds across cellular barriers, influencing their absorption, distribution, and elimination in the body.
-
E.
freight rail corridor
A freight rail corridor is a designated railway route primarily used for the efficient, high-capacity movement of goods and cargo between industrial, commercial, and logistics hubs.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:54 p.m.