Triple
T32807724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSR (Compressed Sparse Row) |
E839061
|
entity |
| Predicate | storageOrder |
P164829
|
FINISHED |
| Object | row-major |
—
|
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: row-major | Statement: [CSR (Compressed Sparse Row), storageOrder, row-major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storageOrder Context triple: [CSR (Compressed Sparse Row), storageOrder, row-major]
-
A.
distributionOrder
Indicates the sequence or arrangement in which items or resources are distributed among recipients or locations.
-
B.
orderingType
chosen
Indicates the specific method or arrangement by which items, events, or entities are ordered or sequenced relative to one another.
-
C.
representationOrder
Indicates the sequence or hierarchy in which representations of entities are arranged or prioritized relative to one another.
-
D.
displayOrder
Indicates the sequence or position in which items should be presented or shown relative to one another.
-
E.
storageOrgan
Indicates that one entity serves as a storage organ (a specialized structure for storing substances like nutrients or water) for 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:15 a.m.