Triple
T35023161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Tokyo Intelligent Space Systems Laboratory |
E1010250
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space engineering laboratory |
C49900
|
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: space engineering laboratory Context triple: [University of Tokyo Intelligent Space Systems Laboratory, instanceOf, space engineering laboratory]
-
A.
space environment simulation laboratory
A space environment simulation laboratory is a controlled facility that recreates key physical conditions of outer space—such as vacuum, radiation, extreme temperatures, and microgravity—to test and study spacecraft components, materials, and biological systems.
-
B.
space research centre
A space research centre is an institution dedicated to the scientific study, exploration, and technological development related to outer space and celestial phenomena.
-
C.
space experiment
A space experiment is a controlled scientific investigation conducted in the unique conditions of outer space or microgravity to study physical, biological, or technological phenomena not observable or easily replicated on Earth.
-
D.
spaceflight center
A spaceflight center is a facility dedicated to the planning, development, testing, and control of spacecraft and space missions.
-
E.
space-focused engineering institute
chosen
A space-focused engineering institute is an educational and research organization dedicated to developing technologies, systems, and expertise for space exploration, satellite applications, and related aerospace industries.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.