Triple
T12760420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waller Flexible Gunnery Trainer team |
E304977
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research and development group |
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 group Context triple: [Waller Flexible Gunnery Trainer team, instanceOf, research and development group]
-
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 team
A research team is a collaborative group of individuals with complementary expertise who systematically investigate questions or problems to generate new knowledge or solutions.
-
C.
research and development activity
Research and development activity is a systematic, creative process undertaken to generate new knowledge, products, processes, or services, or to significantly improve existing ones through experimentation, analysis, and innovation.
-
D.
university research team
A university research team is a collaborative group of faculty, students, and sometimes external partners who systematically investigate specific academic or scientific questions to generate new knowledge and publish their findings.
-
E.
research consortium
A research consortium is a collaborative alliance of multiple organizations or institutions that pool resources, expertise, and infrastructure to conduct joint research toward shared scientific or technological goals.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:28 p.m.