Triple
T10267195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Settings app on iOS |
E240737
|
entity |
| Predicate | allowsPerAppSettings |
P93024
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Settings app on iOS, allowsPerAppSettings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsPerAppSettings Context triple: [Settings app on iOS, allowsPerAppSettings, true]
-
A.
supportsThirdPartyApplications
Indicates that an entity is capable of working with, integrating, or allowing the use of software applications developed by external third parties.
-
B.
allowsAppStorePurchaseSharing
Indicates that an entity permits sharing of app store purchases with other designated users or accounts.
-
C.
permittedActivity
Indicates that a particular action or behavior is allowed or authorized within a given context or under specified rules.
-
D.
hasApp
Indicates that an entity possesses, provides, or is associated with a particular application.
-
E.
allowsLocationSharing
Indicates that one entity permits another entity to share its location information.
- 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2872830819080fdfa816167d04c |
completed | April 7, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ef6e6c81908a8ee52e4d28127b |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d285812c8190ab910dc85c53eebf |
completed | April 7, 2026, 9:46 a.m. |
Created at: April 6, 2026, 11:34 a.m.