Triple
T21572913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Space Station flight control teams |
E532327
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mission operations team |
C8231
|
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: mission operations team Context triple: [International Space Station flight control teams, instanceOf, mission operations team]
-
A.
space operations command
A space operations command is a military or governmental organizational unit responsible for planning, directing, and controlling space-based assets and activities to support national security, communications, navigation, and situational awareness.
-
B.
mission commander
A mission commander is the individual responsible for planning, directing, and overseeing the successful execution and safety of an entire mission and its team.
-
C.
space mission science team
A space mission science team is a multidisciplinary group of scientists and specialists responsible for defining mission objectives, designing experiments, analyzing data, and interpreting scientific results to achieve the mission’s research goals.
-
D.
military mission
A military mission is a coordinated operation undertaken by armed forces to achieve specific strategic, operational, or tactical objectives within defined constraints and rules of engagement.
-
E.
operational unit
chosen
An operational unit is an organized group, department, or component within a larger system that performs specific tasks or functions to achieve defined operational objectives.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:30 p.m.