Triple
T29183180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sad Mac error icon code |
E739796
|
entity |
| Predicate | nonVolatileStorage |
P35145
|
FINISHED |
| Object | read-only memory |
—
|
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: read-only memory | Statement: [Sad Mac error icon code, nonVolatileStorage, read-only memory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonVolatileStorage Context triple: [Sad Mac error icon code, nonVolatileStorage, read-only memory]
-
A.
nonVolatile
chosen
Indicates that the associated entity or state does not change, disappear, or lose its value when power is removed or over time.
-
B.
canBeStoredOn
Indicates that one entity is capable of being placed, kept, or maintained on another entity as a storage location.
-
C.
dataStorage
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
D.
secondaryStorage
Indicates that an entity serves as a secondary (non-primary) storage location or medium for another entity’s data or resources.
-
E.
storageProperty
Indicates a relationship where an entity has a specific storage-related characteristic, such as capacity, type, or configuration.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663850bd88190a41413ffcb3e7924 |
completed | May 2, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:58 a.m.