Triple
T36454137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Instruments Calypso-based phones |
E898102
|
entity |
| Predicate | typicalOS |
P1593
|
FINISHED |
| Object | proprietary RTOS on baseband |
—
|
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: proprietary RTOS on baseband | Statement: [Texas Instruments Calypso-based phones, typicalOS, proprietary RTOS on baseband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOS Context triple: [Texas Instruments Calypso-based phones, typicalOS, proprietary RTOS on baseband]
-
A.
operatorSystem
Indicates a relationship where one entity functions as the operating system that manages or controls another entity (such as a device, application, or system).
-
B.
operatesSystem
Indicates that an entity actively controls, manages, or runs a particular system.
-
C.
operatingSystem
chosen
Indicates that one entity is the operating system running on, or used by, another entity.
-
D.
systemOperatesOn
Indicates that a system performs operations, actions, or processing directly on a specified target or resource.
-
E.
operatingSystemCategory
Indicates the classification or type of operating system that an operating system instance belongs to.
- 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_69f76e57f08481908593bd0bc34581c8 |
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.