Triple
T32820603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-31 Hubble deployment |
E839423
|
entity |
| Predicate | remoteManipulatorSystemUsed |
P37038
|
FINISHED |
| Object | Canadarm |
—
|
NE NERFINISHED |
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: Canadarm | Statement: [STS-31 Hubble deployment, remoteManipulatorSystemUsed, Canadarm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remoteManipulatorSystemUsed Context triple: [STS-31 Hubble deployment, remoteManipulatorSystemUsed, Canadarm]
-
A.
usedRemoteManipulatorSystem
chosen
Indicates that an entity operated or controlled another entity by means of a remote manipulator system.
-
B.
robotControlSystem
Indicates a relationship where a system monitors, directs, and coordinates the actions and behaviors of one or more robots.
-
C.
roverOperator
Indicates a relationship where one entity operates, controls, or manages a rover (such as a robotic exploration vehicle).
-
D.
isFullyRobotic
Indicates that the entity operates entirely through robotic mechanisms without human biological components or manual control.
-
E.
hasAutomatedRendezvousSystem
Indicates that an entity is equipped with a system capable of performing rendezvous operations automatically, without direct human control.
- 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_69f3493df9008190a8f5d843dcd77704 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:15 a.m.