Triple
T17676444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SparseMatrixCSC |
E440652
|
entity |
| Predicate | defaultSparseFormatInJulia |
P128518
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SparseMatrixCSC, defaultSparseFormatInJulia, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultSparseFormatInJulia Context triple: [SparseMatrixCSC, defaultSparseFormatInJulia, true]
-
A.
distributedFormat
Indicates that an entity is made available or disseminated in a particular format or medium.
-
B.
storageFormat
Indicates the specific way in which data or content is physically or logically organized, encoded, and stored.
-
C.
usesSparseInstrumentation
Indicates that an entity performs monitoring or data collection with minimal or selectively placed instrumentation rather than comprehensive coverage.
-
D.
supportsRowFormat
Indicates that one entity provides compatibility with or can correctly handle the specified row format of another entity.
-
E.
defaultPackageFormat
Indicates the standard or primary packaging format that is used by default for an item or distribution.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:01 a.m.