Triple
T6056864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honeywell 200 series |
E134934
|
entity |
| Predicate | typicalPeripherals |
P32413
|
FINISHED |
| Object | magnetic tape drives |
—
|
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: magnetic tape drives | Statement: [Honeywell 200 series, typicalPeripherals, magnetic tape drives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPeripherals Context triple: [Honeywell 200 series, typicalPeripherals, magnetic tape drives]
-
A.
peripheralType
chosen
Indicates the specific category or kind of peripheral device associated with or used by an entity.
-
B.
typicalPlatform
Indicates that something commonly or usually serves as the platform or environment on which another thing operates, appears, or is based.
-
C.
typicalTools
Indicates that the related tools are commonly or characteristically used to perform the associated activity, task, or function.
-
D.
hardwareUsedBy
Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
-
E.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0570bf01c8190a8b2c25b7805d403 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:09 p.m.