Triple
T7932648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloud IAM |
E184219
|
entity |
| Predicate | policyAttachmentLevel |
P9281
|
FINISHED |
| Object | organization |
—
|
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: organization | Statement: [Cloud IAM, policyAttachmentLevel, organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyAttachmentLevel Context triple: [Cloud IAM, policyAttachmentLevel, organization]
-
A.
policyLevel
chosen
Indicates the degree or tier of strictness, scope, or priority associated with a given policy.
-
B.
protectionLevel
Indicates the degree or extent to which something is safeguarded against harm, risk, or unauthorized access.
-
C.
authorizationLevel
Indicates the degree or tier of access rights or permissions granted to an entity within a system or context.
-
D.
protectionPolicy
Indicates that one entity establishes or enforces rules or measures to safeguard another entity from harm, loss, or risk.
-
E.
configurationLevel
Indicates the degree or tier of settings or parameters applied to configure something within a system or context.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3acfd2a88190b1a13cd6fdedc272 |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:08 p.m.