Triple
T31117496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talavera la Real Air Base |
E793131
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Spanish Air and Space Force installation |
C14319
|
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: Spanish Air and Space Force installation Context triple: [Talavera la Real Air Base, instanceOf, Spanish Air and Space Force installation]
-
A.
Spanish Air Force base
chosen
A Spanish Air Force base is a military installation in Spain that supports the operations, training, maintenance, and deployment of the Spanish Air and Space Force’s aircraft and personnel.
-
B.
Spanish Air Force institution
The Spanish Air Force institution is the national military aviation organization of Spain responsible for defending the country’s airspace, conducting aerial operations, and supporting national and international security missions.
-
C.
Portuguese Air Force base
A Portuguese Air Force base is a military installation in Portugal that supports air operations, training, maintenance, and logistics for the Portuguese Air Force.
-
D.
Philippine Air Force installation
A Philippine Air Force installation is a designated military facility or base in the Philippines used by the Philippine Air Force for operations, training, logistics, administration, and support of air defense and related missions.
-
E.
Royal Saudi Air Force installation
A Royal Saudi Air Force installation is a designated military facility in Saudi Arabia used by the Royal Saudi Air Force for operations, training, logistics, maintenance, and support of air power capabilities.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:04 p.m.