Triple
T32807749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSR (Compressed Sparse Row) |
E839061
|
entity |
| Predicate | typicalIndexBase |
—
|
GENERATED |
| Object | 0-based indices |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalIndexBase Context triple: [CSR (Compressed Sparse Row), typicalIndexBase, 0-based indices]
-
A.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
B.
hasBaseIndex
chosen
Indicates that one entity serves as the reference or starting index from which another entity’s position, offset, or ordering is calculated.
-
C.
coreIndex
Indicates the position or identifier of an entity within a central or primary ordered structure (its core sequence or index).
-
D.
indexType
Indicates the classification or category of an index associated with an entity or structure.
-
E.
typicalBaseClass
Indicates that one class is the usual or standard superclass (base class) from which another class is typically derived.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 1, 2026, 1:15 a.m.