Triple
T8287069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HKEY_CLASSES_ROOT |
E193809
|
entity |
| Predicate | containsSubkeysOfType |
P70217
|
FINISHED |
| Object | file extension keys |
—
|
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 extension keys | Statement: [HKEY_CLASSES_ROOT, containsSubkeysOfType, file extension keys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSubkeysOfType Context triple: [HKEY_CLASSES_ROOT, containsSubkeysOfType, file extension keys]
-
A.
hasKeyType
Indicates that an entity possesses or is associated with a specific category or type of key.
-
B.
hasSubset
Indicates that one set is entirely contained within another set, with all elements of the first set also belonging to the second.
-
C.
hasDescendantsType
chosen
Indicates that an entity has descendants belonging to a specified type or category.
-
D.
hasSubOrganizationType
Indicates that an organization is associated with or classified under a specific type or category of sub-organization.
-
E.
hasSubcollection
Indicates that one collection contains another collection as a subordinate or nested part of it.
- 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.