Triple
T3300627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qsuite |
E69320
|
entity |
| Predicate | privacyLevel |
P14409
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Qsuite, privacyLevel, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: privacyLevel Context triple: [Qsuite, privacyLevel, high]
-
A.
privacyProperty
Indicates that one entity has a characteristic, rule, or condition specifically related to privacy in the context of the relationship.
-
B.
disclosureLevel
Indicates the extent or degree to which information is revealed, shared, or made accessible in a given context.
-
C.
privacyCharacteristic
Indicates the specific privacy-related property or feature that characterizes how information is handled, protected, or exposed in a given context.
-
D.
protectionLevel
chosen
Indicates the degree or extent to which something is safeguarded against harm, risk, or unauthorized access.
-
E.
policyLevel
Indicates the degree or tier of strictness, scope, or priority associated with a given policy.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a66fcc819093931fe7a6507723 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.