Triple
T20532839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Air Station Joint Reserve Base Fort Worth |
E504113
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint reserve base |
C1085
|
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: joint reserve base Context triple: [Naval Air Station Joint Reserve Base Fort Worth, instanceOf, joint reserve base]
-
A.
reserve component of the United States Air Force
The reserve component of the United States Air Force is the part-time military force composed of Air Force Reserve and Air National Guard units that support and augment the active-duty Air Force during peacetime and wartime operations.
-
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 Air Force base
chosen
A United States Air Force base is a military installation that supports Air Force operations through facilities for aircraft, personnel, training, logistics, and command and control activities.
-
D.
military base agreement
A military base agreement is a formal arrangement between a host nation and a foreign state that defines the rights, responsibilities, and conditions under which the foreign state may establish, operate, and maintain military facilities on the host nation’s territory.
-
E.
former air force base
A former air force base is a decommissioned military airfield and associated facilities that once supported air force operations but has since been closed, repurposed, or abandoned.
- 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:37 a.m.