Triple
T30247366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indo-Pacific sea lanes of communication |
E769095
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | strategic waterway system |
C3393
|
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: strategic waterway system Context triple: [Indo-Pacific sea lanes of communication, instanceOf, strategic waterway system]
-
A.
waterway navigation system
A waterway navigation system is an integrated set of tools, sensors, and software that provides real-time guidance, routing, and safety information for vessels traveling on rivers, canals, and other inland or coastal waterways.
-
B.
waterway network
A waterway network is an interconnected system of natural and artificial water channels (such as rivers, canals, and streams) designed or utilized for the movement, distribution, and management of water and waterborne transport.
-
C.
navigable waterway
chosen
A navigable waterway is a natural or artificial body of water, such as a river, canal, or channel, that is deep and wide enough for vessels to travel safely for transportation or commerce.
-
D.
engineered waterway
An engineered waterway is a human-made or heavily modified channel or system designed to control, convey, or manage water for purposes such as navigation, irrigation, drainage, flood control, or power generation.
-
E.
maritime convoy system
A maritime convoy system is an organized method of grouping merchant or military vessels to sail together under coordinated protection and navigation to reduce risks from threats such as enemy attacks, piracy, or hazardous conditions.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:39 p.m.