Triple
T24389122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coast Guard Base Portsmouth |
E614834
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Coast Guard base |
C15032
|
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 Coast Guard base Context triple: [Coast Guard Base Portsmouth, instanceOf, United States Coast Guard base]
-
A.
United States Coast Guard facility
chosen
A United States Coast Guard facility is a designated site, such as a station, base, or support installation, used to house personnel, equipment, and operations that support the Coast Guard’s maritime safety, security, law enforcement, and environmental protection missions.
-
B.
Marine Corps base
A Marine Corps base is a military installation that provides facilities, training grounds, housing, and logistical support for United States Marine Corps personnel and operations.
-
C.
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.
-
D.
former naval base
A former naval base is a decommissioned military maritime facility that once supported naval operations but has since been repurposed, abandoned, or converted to civilian use.
-
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_69e2d7e509b88190a53155d4f3de45ce |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:04 a.m.