Triple
T23817808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centre for Airborne Systems |
E589142
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research and development organisation |
C425
|
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: research and development organisation Context triple: [Centre for Airborne Systems, instanceOf, research and development organisation]
-
A.
research and development organization
chosen
A research and development organization is an entity dedicated to systematically investigating ideas and technologies to create new knowledge, products, or processes and improve existing ones.
-
B.
research organization
A research organization is an institution that systematically investigates specific questions or problems to generate new knowledge, technologies, or insights, often within scientific, academic, or applied domains.
-
C.
research and education centre
A research and education centre is an institution dedicated to generating new knowledge through systematic investigation and disseminating it through structured teaching, training, and outreach activities.
-
D.
public research institution
A public research institution is a government-funded organization dedicated to advancing knowledge and innovation through systematic investigation, experimentation, and dissemination of findings for the benefit of society.
-
E.
research and competence centre
A research and competence centre is an organizational unit that conducts advanced studies and develops, concentrates, and disseminates specialized expertise within a particular field to support innovation, education, and practical application.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 7:58 p.m.