Triple
T28899698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wind River Systems |
E732919
|
entity |
| Predicate | notableOperatingSystem |
P1593
|
FINISHED |
| Object | VxWorks real-time operating system |
—
|
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: VxWorks real-time operating system | Statement: [Wind River Systems, notableOperatingSystem, VxWorks real-time operating system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOperatingSystem Context triple: [Wind River Systems, notableOperatingSystem, VxWorks real-time operating system]
-
A.
operatesSystem
Indicates that an entity actively controls, manages, or runs a particular system.
-
B.
operatingSystem
chosen
Indicates that one entity is the operating system running on, or used by, another entity.
-
C.
operatingSystemCategory
Indicates the classification or type of operating system that an operating system instance belongs to.
-
D.
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).
-
E.
notableSystem
Indicates that a system is recognized as significant, prominent, or noteworthy in a particular context or domain.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a01b241f7308190bedb7522cb5dc069 |
completed | May 11, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_6a01b19ff12c81908ee1b188b4a3e118 |
completed | May 11, 2026, 10:38 a.m. |
Created at: April 28, 2026, 8:01 a.m.