Triple
T28033459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOC 3 |
E708333
|
entity |
| Predicate | assuranceLevel |
P148087
|
FINISHED |
| Object | high-level |
—
|
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-level | Statement: [SOC 3, assuranceLevel, high-level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assuranceLevel Context triple: [SOC 3, assuranceLevel, high-level]
-
A.
confidenceLevel
chosen
Indicates the degree of certainty or assurance associated with a particular claim, decision, or outcome.
-
B.
degreeOfAttestation
Indicates the extent or level to which something (such as a claim, form, or document) is supported, verified, or confirmed by evidence or authoritative sources.
-
C.
certificationLevel
Indicates the specific rank or degree of formal qualification or authorization that an entity has achieved within a defined certification system.
-
D.
hasStabilityLevel
Indicates that something possesses a particular degree or state of stability, often quantified or categorized along a defined scale.
-
E.
legalAuthorityLevel
Indicates the degree or rank of formal legal power or jurisdiction an entity holds in relation to another or within a given 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63c7507dc81909db7f9b46f012c76 |
completed | May 2, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:18 p.m.