Triple
T26638076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iomega |
E668694
|
entity |
| Predicate | focusAfterAcquisition |
P96211
|
FINISHED |
| Object | network storage |
—
|
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: network storage | Statement: [Iomega, focusAfterAcquisition, network storage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusAfterAcquisition Context triple: [Iomega, focusAfterAcquisition, network storage]
-
A.
focusAfterTransition
Indicates that focus is moved to a specific element or area after a transition or state change has completed.
-
B.
focusShift
chosen
Indicates a change in attention or emphasis from one entity or topic to another.
-
C.
focusOf
Indicates that one entity is the primary subject, target, or center of attention, activity, or interest for another entity.
-
D.
focusAfterRelaunch
Indicates that an entity regains or receives input focus after an application or process has been relaunched.
-
E.
focusTrait
Indicates that one entity is characterized by, or primarily associated with, a particular trait or attribute of 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 2:28 a.m.