Triple
T17676405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SparseMatrixCSC |
E440652
|
entity |
| Predicate | usesStorageFormat |
P109452
|
FINISHED |
| Object | compressed sparse column |
—
|
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: compressed sparse column | Statement: [SparseMatrixCSC, usesStorageFormat, compressed sparse column]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStorageFormat Context triple: [SparseMatrixCSC, usesStorageFormat, compressed sparse column]
-
A.
storageFormat
Indicates the specific way in which data or content is physically or logically organized, encoded, and stored.
-
B.
usedFormat
chosen
Indicates that one entity employs or applies a particular format or representation in relation to another entity.
-
C.
hasStorage
Indicates that one entity provides or contains storage capacity or space for another entity or resource.
-
D.
hasStorageFunction
Indicates that an entity serves to store, retain, or hold another entity or resource for later use.
-
E.
usedInFormat
Indicates that something (such as a method, standard, or component) is employed or applied within a particular format.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6d9ab88190ab0e25eac8b0101c |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:01 a.m.