Triple
T5560914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Propulsion Research Laboratory |
E145762
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aerospace research laboratory |
C5661
|
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: aerospace research laboratory Context triple: [Propulsion Research Laboratory, instanceOf, aerospace research laboratory]
-
A.
U.S. Army research laboratory
The U.S. Army Research Laboratory is the Army’s primary scientific and engineering research organization, conducting foundational and applied research to develop advanced technologies that enhance the capabilities, effectiveness, and protection of U.S. soldiers.
-
B.
aerospace corporation
An aerospace corporation is a large-scale enterprise that designs, manufactures, and services aircraft, spacecraft, and related systems and technologies for commercial, military, and space applications.
-
C.
rocket research institute
A rocket research institute is an organization dedicated to the scientific study, design, testing, and advancement of rocket technologies and related space propulsion systems.
-
D.
naval research laboratory
A naval research laboratory is a specialized scientific and engineering institution dedicated to developing, testing, and evaluating technologies and systems to support and advance a nation's maritime and naval capabilities.
-
E.
aerospace organization
chosen
An aerospace organization is an entity that researches, designs, manufactures, operates, or supports aircraft, spacecraft, and related systems and technologies for commercial, governmental, or defense purposes.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:36 p.m.