Triple
T29747515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo DN450 |
E752795
|
entity |
| Predicate | hardwareClass |
P9899
|
FINISHED |
| Object | technical workstation |
—
|
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: technical workstation | Statement: [Apollo DN450, hardwareClass, technical workstation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hardwareClass Context triple: [Apollo DN450, hardwareClass, technical workstation]
-
A.
hardwarePlatformFor
Indicates that one entity serves as the hardware platform on which another entity is designed to run or be deployed.
-
B.
hardwareComponent
Indicates that one entity is a physical hardware part or module that is contained in, attached to, or functionally part of another hardware system or device.
-
C.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
-
D.
hardwareRole
chosen
Indicates the functional role or purpose that a piece of hardware serves within a system or configuration.
-
E.
hardwareUsedBy
Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67368906c81908fbdad28b9fd300d |
completed | May 2, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:51 p.m.