Triple
T4771504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans-Alaska Pipeline System |
E105936
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pipeline transportation infrastructure |
C3206
|
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: pipeline transportation infrastructure Context triple: [Trans-Alaska Pipeline System, instanceOf, pipeline transportation infrastructure]
-
A.
tank transmission
A tank transmission is a mechanical system that transfers power from the tank’s engine to its tracks, enabling controlled movement, speed changes, and maneuvering under varying terrain and load conditions.
-
B.
tank transmission
A tank transmission is a complex drivetrain component that transfers engine power to a tank’s tracks, enabling controlled movement, speed changes, and steering under heavy load and rough terrain conditions.
-
C.
rail transportation infrastructure
Rail transportation infrastructure encompasses the physical and organizational systems—such as tracks, stations, signaling, power supply, and related facilities—required to support the safe and efficient movement of trains and rail-based services.
-
D.
transport infrastructure network
A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
-
E.
infrastructure
chosen
Infrastructure is the foundational physical and organizational systems—such as transportation, utilities, communication networks, and public facilities—that enable a society or organization to function and grow.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:21 p.m.