Triple
T28390897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WSearch |
E719152
|
entity |
| Predicate | indexLocation |
P164700
|
FINISHED |
| Object | system drive by default |
—
|
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: system drive by default | Statement: [WSearch, indexLocation, system drive by default]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indexLocation Context triple: [WSearch, indexLocation, system drive by default]
-
A.
indexMovement
Indicates a change in the value or level of an index (such as a financial, economic, or performance index) over time.
-
B.
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.
-
C.
indexed
Indicates that one entity is organized, recorded, or referenced within a systematic index or catalog relative to another entity.
-
D.
indexType
Indicates the classification or category of an index associated with an entity or structure.
-
E.
indexMethod
Indicates the method or technique used to create, organize, or access an index for a given resource or dataset.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64ee0c2788190a94a04ad1902fd5e |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64e36c57c8190af09470a8d35512b |
completed | May 2, 2026, 7:19 p.m. |
Created at: April 28, 2026, 1:13 a.m.