Triple
T26071507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jones Point Reserve Fleet |
E657558
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Navy anchorage |
C21546
|
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: United States Navy anchorage Context triple: [Jones Point Reserve Fleet, instanceOf, United States Navy anchorage]
-
A.
National Defense Reserve Fleet anchorage
chosen
A National Defense Reserve Fleet anchorage is a designated harbor area where the U.S. government moors and maintains inactive merchant and military support vessels for rapid activation during national emergencies or defense needs.
-
B.
naval anchorage network
A naval anchorage network is an interconnected system of designated maritime anchor points, supporting infrastructure, and communication links that enables coordinated deployment, resupply, and protection of naval vessels across strategic sea areas.
-
C.
naval shore establishment
A naval shore establishment is a land-based facility that supports a navy’s operations, administration, training, logistics, and maintenance away from seagoing vessels.
-
D.
United States Navy air station
A United States Navy air station is a shore-based military aviation facility operated by the U.S. Navy that supports the operation, training, maintenance, and deployment of naval aircraft and their personnel.
-
E.
United States Navy submarine base
A United States Navy submarine base is a secure naval installation that supports the homeporting, maintenance, logistics, training, and operational deployment of U.S. Navy submarines and their crews.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:29 p.m.