Triple
T31583915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DG/UX |
E805896
|
entity |
| Predicate | targetHardwarePlatform |
P55922
|
FINISHED |
| Object | Data General AViiON |
—
|
NE NERFINISHED |
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: Data General AViiON | Statement: [DG/UX, targetHardwarePlatform, Data General AViiON]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetHardwarePlatform Context triple: [DG/UX, targetHardwarePlatform, Data General AViiON]
-
A.
hardwarePlatformFor
chosen
Indicates that one entity serves as the hardware platform on which another entity is designed to run or be deployed.
-
B.
targetPlatformGeneration
Indicates the generation or version of the platform that an action, resource, or entity is specifically intended to run on or be compatible with.
-
C.
supportedPlatform
Indicates that one entity (such as a system, application, or service) is compatible with and can operate on a particular platform.
-
D.
targetPlatformFeature
Indicates that a particular feature is available on, or specifically associated with, a given target platform.
-
E.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: April 30, 2026, 10:24 p.m.