Triple
T33013099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sego |
E844696
|
entity |
| Predicate | operatorInput |
P147459
|
FINISHED |
| Object | manual command to missile via joystick or control box |
—
|
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: manual command to missile via joystick or control box | Statement: [Sego, operatorInput, manual command to missile via joystick or control box]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorInput Context triple: [Sego, operatorInput, manual command to missile via joystick or control box]
-
A.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
B.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
C.
operatorUse
chosen
Indicates that an operator or tool is being used or applied by one entity to act upon or interact with another entity.
-
D.
operate
Indicates that an agent performs, manages, or controls the functioning of a system, device, or process.
-
E.
operatorStart
Indicates the point in time or event at which an operator begins performing an action or process.
- 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a005d878aec81908e1177914a8fb610 |
completed | May 10, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_6a005c382f8881908ff33ebb7f88c430 |
completed | May 10, 2026, 10:21 a.m. |
Created at: May 1, 2026, 1:23 a.m.