Triple
T16602881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPIC system |
E403372
|
entity |
| Predicate | hardwareEra |
P50875
|
FINISHED |
| Object | mainframe computers |
—
|
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: mainframe computers | Statement: [UPIC system, hardwareEra, mainframe computers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hardwareEra Context triple: [UPIC system, hardwareEra, mainframe computers]
-
A.
notablePlatformEra
chosen
Indicates that an entity is notably associated with a particular platform during a specific era or period of prominence.
-
B.
introducedHardware
Indicates that an entity caused a particular piece of hardware to be brought into use or made available for the first time.
-
C.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
-
D.
technologyLegacy
Indicates that one entity has inherited, retained, or is influenced by the past technologies, systems, or technical decisions associated with another entity.
-
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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d770a048190be42180b03efba0b |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.