Triple
T36896971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAE Aberporth |
E911916
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Aircraft Establishment outstation |
C59740
|
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 Aircraft Establishment outstation Context triple: [RAE Aberporth, instanceOf, Royal Aircraft Establishment outstation]
-
A.
Royal Air Force maintenance unit
A Royal Air Force maintenance unit is a specialized organizational entity responsible for the inspection, repair, servicing, and logistical support of RAF aircraft and related equipment to ensure operational readiness and safety.
-
B.
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.
-
C.
Royal Air Force installation
chosen
A Royal Air Force installation is a designated military facility used by the United Kingdom's Royal Air Force for operations, training, support, and administration of air power activities.
-
D.
Royal Air Force operational training unit
A Royal Air Force operational training unit is a specialized formation responsible for converting trained aircrew and ground personnel to specific aircraft types and preparing them for front-line operational duties.
-
E.
Royal Air Force signals unit
A Royal Air Force signals unit is a specialized military formation responsible for establishing, operating, and protecting communications and information systems that support RAF command, control, and operations.
- 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.