Triple
T34985111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Party Assessment Organizations |
E1008922
|
entity |
| Predicate | assessmentScope |
P51335
|
FINISHED |
| Object | cloud system boundary |
—
|
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: cloud system boundary | Statement: [Third Party Assessment Organizations, assessmentScope, cloud system boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assessmentScope Context triple: [Third Party Assessment Organizations, assessmentScope, cloud system boundary]
-
A.
coverageScope
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
-
B.
acquisitionScope
Indicates the extent, boundaries, or coverage of what is obtained or brought under control through an acquisition.
-
C.
accessScope
Indicates the extent or boundaries of access that one entity has to another entity or resource.
-
D.
reviewScope
chosen
Indicates the extent, boundaries, or aspects of something that are covered, considered, or evaluated during a review.
-
E.
availabilityScope
Indicates the extent or context within which something is available, accessible, or applicable.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.