Triple
T9299247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA flight test operations |
E223718
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research and development activity |
C27169
|
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 activity Context triple: [NASA flight test operations, instanceOf, research and development activity]
-
A.
research and development organization
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 initiative
A research initiative is a coordinated, goal-driven effort to investigate specific questions or problems, typically organized around a defined scope, methodology, timeline, and set of expected outcomes.
-
C.
research facility
A research facility is a specialized institution equipped with laboratories, instruments, and resources where scientists and experts systematically investigate, experiment, and develop new knowledge or technologies.
-
D.
research project
A research project is a structured, systematic investigation designed to answer specific questions or test hypotheses by collecting, analyzing, and interpreting data within a defined scope and timeframe.
-
E.
collaborative research and development agreement
A collaborative research and development agreement is a contract between two or more parties that defines how they will jointly conduct R&D activities, share resources, allocate intellectual property rights, and manage risks and responsibilities.
- F. None of above. chosen
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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:36 p.m.