Triple
T27561139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows component store |
E695770
|
entity |
| Predicate | fileSystemPathType |
P138781
|
FINISHED |
| Object | system folder |
—
|
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 folder | Statement: [Windows component store, fileSystemPathType, system folder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fileSystemPathType Context triple: [Windows component store, fileSystemPathType, system folder]
-
A.
fileSystemFamily
Indicates that two file systems belong to the same family or type, sharing a common design, lineage, or implementation characteristics.
-
B.
fileSystemProperty
Indicates a characteristic, attribute, or configuration setting associated with a file system.
-
C.
fileSystemFullName
Indicates the complete, fully qualified name or path of a file system within a storage or operating system context.
-
D.
isPathType
chosen
Indicates that a given entity represents a type or category of path within a system or domain.
-
E.
filenameType
Indicates the type or category associated with a given filename (e.g., file format, role, or classification).
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62fb974e08190a01b9c243e9e8193 |
completed | May 2, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:39 p.m.