Triple
T28854897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearl Harbor Naval Base infrastructure |
E728708
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military base infrastructure |
C1086
|
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: military base infrastructure Context triple: [Pearl Harbor Naval Base infrastructure, instanceOf, military base infrastructure]
-
A.
military installation
chosen
A military installation is a designated facility or area where armed forces are stationed, trained, equipped, and supported to conduct defense and security operations.
-
B.
military base network
A military base network is an interconnected system of communication, data, and operational infrastructure linking facilities, units, and resources across one or more military installations to support command, control, logistics, and security functions.
-
C.
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.
-
D.
military-security structure
A military-security structure is an organized system of forces, institutions, and mechanisms designed to protect a state or entity from external and internal threats through defense, intelligence, and enforcement capabilities.
-
E.
military training infrastructure network
A military training infrastructure network is an integrated system of facilities, ranges, technologies, and support services designed to plan, deliver, and sustain training activities for armed forces across multiple locations.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:45 a.m.