Triple
T36485889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microgravity Science Glovebox |
E898930
|
entity |
| Predicate | hasControlMode |
P98668
|
FINISHED |
| Object | astronaut-operated |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: astronaut-operated | Statement: [Microgravity Science Glovebox, hasControlMode, astronaut-operated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControlMode Context triple: [Microgravity Science Glovebox, hasControlMode, astronaut-operated]
-
A.
hasControlService
Indicates that one entity provides or performs a control-related service for another entity.
-
B.
hasControlScheme
chosen
Indicates that one entity defines or uses a particular control scheme or input configuration associated with another entity.
-
C.
hasWorkingMode
Indicates that an entity operates under or supports a particular mode or configuration of functioning.
-
D.
isRemoteControlled
Indicates that an entity is operated or controlled from a distance via a remote device or system.
-
E.
hasManualControls
Indicates that an entity is equipped with controls intended to be operated directly by a human user.
- F. None of above.
Provenance (3 batches)
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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.