Triple
T5451905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Control |
E122388
|
entity |
| Predicate | textInput |
P8613
|
FINISHED |
| Object | single keyboard for text entry on multiple devices |
—
|
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: single keyboard for text entry on multiple devices | Statement: [Universal Control, textInput, single keyboard for text entry on multiple devices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textInput Context triple: [Universal Control, textInput, single keyboard for text entry on multiple devices]
-
A.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
B.
input
Indicates that one entity provides data, signals, or resources that are received or processed by another entity.
-
C.
textType
Indicates the classification of a text according to its type, format, or genre.
-
D.
primaryInput
Indicates that an entity serves as the main or principal input to a process, system, or operation.
-
E.
textMode
chosen
Indicates that something operates, is displayed, or is processed in a mode where information is handled primarily as text rather than as graphics or other media.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.