Triple
T15976886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RMAF Butterworth Air Base |
E387471
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Malaysian Air Force base |
C36774
|
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 Malaysian Air Force base Context triple: [RMAF Butterworth Air Base, instanceOf, Royal Malaysian Air Force base]
-
A.
Royal Thai Air Force base
A Royal Thai Air Force base is a military airfield operated by the Royal Thai Air Force that supports air operations, training, logistics, and defense activities within Thailand and, when required, abroad.
-
B.
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.
-
C.
Indian Air Force station
An Indian Air Force station is a permanent military airbase facility operated by the Indian Air Force that supports aircraft operations, training, logistics, and administrative functions for air defense and related missions.
-
D.
Iraqi Air Force base
An Iraqi Air Force base is a military airfield in Iraq that supports air operations through facilities for aircraft deployment, maintenance, training, logistics, and command and control.
-
E.
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.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:54 a.m.