Triple
T30315530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Gatekeeper |
E771045
|
entity |
| Predicate | settingOption |
P28533
|
FINISHED |
| Object | Allow apps from App Store |
—
|
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: Allow apps from App Store | Statement: [Apple Gatekeeper, settingOption, Allow apps from App Store]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOption Context triple: [Apple Gatekeeper, settingOption, Allow apps from App Store]
-
A.
settingChange
Indicates a change made to a configuration, environment, or parameter value from one state to another.
-
B.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
C.
configurationOptionIn
chosen
Indicates that a specific configuration option belongs to, or is defined within, a particular configuration set, context, or system.
-
D.
settingOfControl
Indicates that one entity is the context or environment in which another entity exercises control or governance.
-
E.
featuresSetting
Indicates that something includes, presents, or highlights a particular setting as a notable or primary aspect.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 29, 2026, 7:51 p.m.