Triple
T28615661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GetDeviceCaps |
E724266
|
entity |
| Predicate | indexParameterUses |
P165474
|
FINISHED |
| Object | predefined constants |
—
|
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: predefined constants | Statement: [GetDeviceCaps, indexParameterUses, predefined constants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indexParameterUses Context triple: [GetDeviceCaps, indexParameterUses, predefined constants]
-
A.
indexUsedBy
Indicates that a particular index is utilized or referenced by another entity, such as a query, process, or data structure.
-
B.
usedInIndex
Indicates that something is utilized or referenced within a particular index or indexing structure.
-
C.
definitionUses
Indicates that one definition makes use of, depends on, or references another definition.
-
D.
indexMethod
Indicates the method or technique used to create, organize, or access an index for a given resource or dataset.
-
E.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 28, 2026, 4:31 a.m.