Triple
T8287116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Programs and Features |
E193810
|
entity |
| Predicate | accessPath |
P82537
|
FINISHED |
| Object | Control Panel → Programs → Programs and Features |
—
|
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: Control Panel → Programs → Programs and Features | Statement: [Programs and Features, accessPath, Control Panel → Programs → Programs and Features]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessPath Context triple: [Programs and Features, accessPath, Control Panel → Programs → Programs and Features]
-
A.
accessURL
Indicates the web address or endpoint through which a resource can be accessed or retrieved.
-
B.
accessDirection
Indicates the direction or orientation from which access to something is obtained or permitted.
-
C.
accessMethod
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
D.
accessPattern
Indicates how an entity interacts with or retrieves data or resources, such as the manner, frequency, or sequence of access.
-
E.
accessDeterminedBy
Indicates that the ability to access a resource is governed or controlled by a specified condition, rule, or authority.
- 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_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. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:52 p.m.