Triple
T17676420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SparseMatrixCSC |
E440652
|
entity |
| Predicate | rowIndexing |
P128513
|
FINISHED |
| Object | 1-based |
—
|
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: 1-based | Statement: [SparseMatrixCSC, rowIndexing, 1-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rowIndexing Context triple: [SparseMatrixCSC, rowIndexing, 1-based]
-
A.
indexed
Indicates that one entity is organized, recorded, or referenced within a systematic index or catalog relative to another entity.
-
B.
raisesIndicesOf
Indicates that one entity increases or elevates the index values or positions associated with another entity.
-
C.
rows
Indicates that one entity is arranged in a horizontal line or sequence relative to another, typically as part of a grid or tabular structure.
-
D.
indexMovement
Indicates a change in the value or level of an index (such as a financial, economic, or performance index) over time.
-
E.
indexStructure
Indicates that one entity serves as an index or organizational framework that structures, arranges, or provides access to another entity or set of entities.
- 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.