Triple
T8287046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HKEY_CLASSES_ROOT |
E193809
|
entity |
| Predicate | storesInformationAbout |
P61555
|
FINISHED |
| Object | file associations |
—
|
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: file associations | Statement: [HKEY_CLASSES_ROOT, storesInformationAbout, file associations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesInformationAbout Context triple: [HKEY_CLASSES_ROOT, storesInformationAbout, file associations]
-
A.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
B.
storesMetadataIn
chosen
Indicates that one entity holds or maintains descriptive or configuration metadata about another entity within a specified storage location or system.
-
C.
reportedlyStores
Indicates that an entity is said or believed, based on reports or claims, to store or hold another entity, without confirming that this storage actually occurs.
-
D.
store
Indicates that one entity keeps or holds another entity in a place or system for future use or access.
-
E.
collectsInformationOn
Indicates that one entity gathers or acquires data, facts, or details about 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad4b2008190ad1624e1335147c6 |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:52 p.m.