Triple
T23635472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RNZAF Base Woodbourne |
E583730
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal New Zealand Air Force base |
C47896
|
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: Royal New Zealand Air Force base Context triple: [RNZAF Base Woodbourne, instanceOf, Royal New Zealand Air Force base]
-
A.
New Zealand Army base
A New Zealand Army base is a secured military installation where New Zealand Defence Force personnel live, train, plan, and support land operations and national defense activities.
-
B.
Royal Canadian Air Force base
A Royal Canadian Air Force base is a military installation operated by the Royal Canadian Air Force that supports air operations, training, maintenance, and administration for Canada’s air defence and aerospace missions.
-
C.
South African Air Force base
A South African Air Force base is a military installation that supports the South African Air Force’s operational, training, logistical, and administrative activities, including the housing, maintenance, and deployment of aircraft and personnel.
-
D.
Royal Netherlands Air Force base
A Royal Netherlands Air Force base is a military airfield facility in the Netherlands used by the Royal Netherlands Air Force for housing aircraft, personnel, operations, training, and support activities.
-
E.
Royal Naval Air Service station
A Royal Naval Air Service station is a military airfield or base operated by the Royal Naval Air Service for the deployment, maintenance, and support of naval aircraft and aircrew.
- F. None of above. chosen
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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:47 p.m.