Triple
T27730576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamerscore |
E697419
|
entity |
| Predicate | supportsPrivacySettings |
P15698
|
FINISHED |
| Object | profile visibility controls |
—
|
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: profile visibility controls | Statement: [Gamerscore, supportsPrivacySettings, profile visibility controls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPrivacySettings Context triple: [Gamerscore, supportsPrivacySettings, profile visibility controls]
-
A.
supportsPrivacySolution
Indicates that one entity endorses, enables, or provides backing for a particular privacy-preserving solution or mechanism.
-
B.
privacyProperty
chosen
Indicates that one entity has a characteristic, rule, or condition specifically related to privacy in the context of the relationship.
-
C.
privacyProtocolsInclude
Indicates that certain privacy protocols encompass, contain, or make use of specified measures, rules, or components.
-
D.
dataProtectionFeature
Indicates a feature or mechanism designed to safeguard data from unauthorized access, alteration, loss, or misuse.
-
E.
supportsPrivilege
Indicates that one entity enables, upholds, or grants a particular privilege or special right to another entity.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ffb5c373948190a6606e8caa87a384 |
completed | May 9, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ffb261da788190b41399df8ed895e8 |
completed | May 9, 2026, 10:17 p.m. |
Created at: April 27, 2026, 3:11 p.m.