Triple
T17561236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ST_Within |
E427698
|
entity |
| Predicate | indexSupport |
P105405
|
FINISHED |
| Object | can use spatial indexes for performance |
—
|
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: can use spatial indexes for performance | Statement: [ST_Within, indexSupport, can use spatial indexes for performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indexSupport Context triple: [ST_Within, indexSupport, can use spatial indexes for performance]
-
A.
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.
-
B.
indexUsedBy
chosen
Indicates that a particular index is utilized or referenced by another entity, such as a query, process, or data structure.
-
C.
indexType
Indicates the classification or category of an index associated with an entity or structure.
-
D.
coreIndex
Indicates the position or identifier of an entity within a central or primary ordered structure (its core sequence or index).
-
E.
indexed
Indicates that one entity is organized, recorded, or referenced within a systematic index or catalog relative to 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e456267e208190a1238fbe1a535bb0 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.