Triple
T2189171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Computer Command System |
E49820
|
entity |
| Predicate | commandOutput |
P30797
|
FINISHED |
| Object | control signals to subsystems |
—
|
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: control signals to subsystems | Statement: [Computer Command System, commandOutput, control signals to subsystems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandOutput Context triple: [Computer Command System, commandOutput, control signals to subsystems]
-
A.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
B.
commandLineTool
Indicates that an entity is a software utility intended to be executed and interacted with via a text-based command-line interface.
-
C.
commandName
Indicates the specific label or identifier used to denote a particular command within a system or interface.
-
D.
compositeOutputStandard
chosen
Indicates that the entity conforms to or is produced according to a specified composite output standard that defines how multiple outputs are structured or combined.
-
E.
commandProcessor
Indicates that one entity is responsible for receiving, interpreting, and executing commands issued by another entity.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.