Triple
T32807749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSR (Compressed Sparse Row) |
E839061
|
entity |
| Predicate | typicalIndexBase |
P25266
|
FINISHED |
| Object | 0-based indices |
—
|
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: 0-based indices | Statement: [CSR (Compressed Sparse Row), typicalIndexBase, 0-based indices]
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 (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_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:15 a.m.