Triple
T34305900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Base d’aéronautique navale de Landivisiau |
E880306
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French Naval Aviation base |
C16023
|
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: French Naval Aviation base Context triple: [Base d’aéronautique navale de Landivisiau, instanceOf, French Naval Aviation base]
-
A.
naval air station
chosen
A naval air station is a military airfield operated by a navy, providing facilities for the operation, maintenance, training, and support of naval aircraft and their personnel.
-
B.
United States Navy air station
A United States Navy air station is a shore-based military aviation facility operated by the U.S. Navy that supports the operation, training, maintenance, and deployment of naval aircraft and their personnel.
-
C.
French naval archival service
The French naval archival service is the governmental institution responsible for collecting, preserving, organizing, and providing access to historical and administrative records related to France’s naval and maritime activities.
-
D.
Indian naval air station
An Indian naval air station is a shore-based military aviation facility of the Indian Navy that supports, operates, and maintains naval aircraft for maritime defense, surveillance, and related operations.
-
E.
Belgian Air Component base
A Belgian Air Component base is a military airfield or installation in Belgium that supports the operations, training, maintenance, and administration of the Belgian Air Component’s aircraft and personnel.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:57 a.m.