Triple
T27561080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Resource Protection |
E695769
|
entity |
| Predicate | repairSource |
P409
|
FINISHED |
| Object | cached copies in component store |
—
|
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: cached copies in component store | Statement: [Windows Resource Protection, repairSource, cached copies in component store]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repairSource Context triple: [Windows Resource Protection, repairSource, cached copies in component store]
-
A.
repairs
Indicates that one entity fixes, restores, or maintains another entity to a proper or functional condition.
-
B.
materialSource
Indicates that one entity serves as the origin or provider of the material or substance used by another entity.
-
C.
repairedIn
Indicates that an item or object underwent repair within a specified location or during a particular time period.
-
D.
source
chosen
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
E.
repairDate
Indicates the date on which a repair action was performed or is scheduled to be performed on an 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 1:39 p.m.