Triple
T28613861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HKEY_CURRENT_CONFIG |
E724230
|
entity |
| Predicate | hasRootKeyName |
P181656
|
FINISHED |
| Object | HKEY_CURRENT_CONFIG |
—
|
NE NERFINISHED |
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: HKEY_CURRENT_CONFIG | Statement: [HKEY_CURRENT_CONFIG, hasRootKeyName, HKEY_CURRENT_CONFIG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRootKeyName Context triple: [HKEY_CURRENT_CONFIG, hasRootKeyName, HKEY_CURRENT_CONFIG]
-
A.
hasRootName
Indicates that an entity is associated with a fundamental or original name from which its other names or forms are derived.
-
B.
hasRootSystem
Indicates that one entity possesses or is characterized by a particular type of root system.
-
C.
hasRootServerHostname
Indicates that an entity is associated with, or identified by, the hostname of its root server.
-
D.
hasWellAtRoot
Indicates that an entity possesses or has a well located at its root or base.
-
E.
hasRootType
Indicates that an entity possesses or is associated with a primary or fundamental type that serves as its root classification.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: April 28, 2026, 4:31 a.m.