Triple
T1308294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Science Mission Directorate |
E27930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | science organization unit |
C56
|
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: science organization unit Context triple: [NASA Science Mission Directorate, instanceOf, science organization unit]
-
A.
research organization
A research organization is an institution that systematically investigates specific questions or problems to generate new knowledge, technologies, or insights, often within scientific, academic, or applied domains.
-
B.
science agency
chosen
A science agency is an organization, typically governmental or intergovernmental, that funds, coordinates, and oversees scientific research and development to advance knowledge and inform policy.
-
C.
intelligence organization unit
An intelligence organization unit is a structured group within an intelligence agency responsible for collecting, analyzing, and disseminating information to support decision-making and security objectives.
-
D.
division of a scientific society
A division of a scientific society is a specialized subunit within the society that focuses on a particular discipline, topic, or professional interest, organizing activities, research, and member services related to that area.
-
E.
organizational unit of IEEE
An organizational unit of IEEE is a formally recognized group within the IEEE structure, such as a society, council, region, section, chapter, or committee, that carries out specific professional, technical, or administrative functions in support of IEEE’s mission.
- 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
Created at: March 1, 2026, 7:51 p.m.