Triple
T28613799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HKEY_CURRENT_USER |
E724229
|
entity |
| Predicate | isLoadedAt |
P105721
|
FINISHED |
| Object | user logon |
—
|
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: user logon | Statement: [HKEY_CURRENT_USER, isLoadedAt, user logon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLoadedAt Context triple: [HKEY_CURRENT_USER, isLoadedAt, user logon]
-
A.
canBeLoadedAt
Indicates that an entity is capable of being placed onto or into another entity (such as a vehicle, container, or system) at a specific location or point in time.
-
B.
loadedWith
Indicates that one entity is carrying, filled with, or heavily supplied with another entity.
-
C.
compiledAt
Indicates that one entity was built or transformed into an executable or final form at a specific time or location represented by the other entity.
-
D.
isHeldAt
chosen
Indicates that an event, state, or condition occurs or is in effect at a specific time or temporal point.
-
E.
canBeLoadedBy
Indicates that one entity is capable of being loaded, initialized, or brought into use by 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:31 a.m.