Triple
T27343570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Ames Research Center arc-jet facilities |
E684172
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ground-test facility |
C7750
|
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: ground-test facility Context triple: [NASA Ames Research Center arc-jet facilities, instanceOf, ground-test facility]
-
A.
testing facility
chosen
A testing facility is a specialized environment equipped with tools, equipment, and procedures designed to systematically evaluate, measure, and validate the performance, safety, or quality of products, systems, or processes.
-
B.
weapons testing facility
A weapons testing facility is a secure, controlled site where weapons and related systems are developed, evaluated, and tested for performance, safety, and reliability.
-
C.
ground tracking facility
A ground tracking facility is a terrestrial station equipped with antennas, sensors, and communication systems used to monitor, communicate with, and control spacecraft or other remote vehicles.
-
D.
ground-based monitoring facility
A ground-based monitoring facility is a terrestrial installation equipped with sensors, instruments, and communication systems used to continuously observe, measure, and report on environmental, geological, atmospheric, or infrastructural conditions.
-
E.
flight test center
A flight test center is a specialized facility where aircraft, spacecraft, or related systems are systematically tested, evaluated, and validated under controlled conditions to ensure performance, safety, and regulatory compliance.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 11:44 a.m.