Triple
T31582443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VAX minicomputer |
E805862
|
entity |
| Predicate | notableOS |
P207463
|
FINISHED |
| Object | VAX/VMS |
E229929
|
NE 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: VAX/VMS | Statement: [VAX minicomputer, notableOS, VAX/VMS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOS Context triple: [VAX minicomputer, notableOS, VAX/VMS]
-
A.
notableSystem
Indicates that a system is recognized as significant, prominent, or noteworthy in a particular context or domain.
-
B.
notableApp
Indicates that an application is recognized as significant, prominent, or noteworthy in some context.
-
C.
notableApplicationDevelopedOn
Indicates that a notable software application was created or built to run on a particular platform, system, or technology.
-
D.
notableInstallation
Indicates that one entity has a significant or noteworthy installation of another entity, such as a prominent display, setup, or implementation.
-
E.
notablePackage
Indicates that an entity is a particularly significant, well-known, or otherwise noteworthy package within its domain.
- F. None of above. chosen
Provenance (5 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b564c30f08190ad3751888ca7da18 |
completed | June 12, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 10:24 p.m.