Triple
T15131804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Active Edge |
E361437
|
entity |
| Predicate | hasUserSetting |
P117442
|
FINISHED |
| Object | enable or disable feature |
—
|
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: enable or disable feature | Statement: [Active Edge, hasUserSetting, enable or disable feature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUserSetting Context triple: [Active Edge, hasUserSetting, enable or disable feature]
-
A.
hasSetting
Indicates that an entity takes place, occurs, or exists within a particular environment, context, or location.
-
B.
hasSettingRole
Indicates that an entity participates in a setting by fulfilling a specific contextual or functional role within it.
-
C.
hasHistoricSetting
Indicates that something is set in, or takes place within, a historically significant time period or location.
-
D.
hasNotableSettingBy
Indicates that the subject has a notable or significant setting that was created, designed, or established by the specified entity.
-
E.
hasUser
Indicates that an entity is associated with or linked to a specific user.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b194748190801e3956bf2429d4 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:06 a.m.