Triple
T28899693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wind River Systems |
E732919
|
entity |
| Predicate | softwareUsedIn |
P100214
|
FINISHED |
| Object | avionics systems |
—
|
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: avionics systems | Statement: [Wind River Systems, softwareUsedIn, avionics systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareUsedIn Context triple: [Wind River Systems, softwareUsedIn, avionics systems]
-
A.
programUsed
Indicates that a particular program, software, or application was employed or utilized in performing an action or achieving a result.
-
B.
toolUsed
Indicates that an action or task is performed using a particular tool as the means or instrument.
-
C.
softwareFor
chosen
Indicates that one entity is designed, intended, or used to operate on, support, or be compatible with another entity as software.
-
D.
commonSoftwareTools
Indicates that the related entities use or are associated with the same software tools.
-
E.
softwareSystem
Indicates a relationship where an entity functions as, or is classified as, a software system.
- 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_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 8:01 a.m.