Triple
T28033473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOC 3 |
E708333
|
entity |
| Predicate | differenceFromSOC2 |
P164386
|
FINISHED |
| Object | less technical detail |
—
|
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: less technical detail | Statement: [SOC 3, differenceFromSOC2, less technical detail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differenceFromSOC2 Context triple: [SOC 3, differenceFromSOC2, less technical detail]
-
A.
differenceFromSidecar
Indicates that one entity differs in some specified way from a corresponding or reference entity referred to as a "sidecar."
-
B.
differenceFromRSA
Indicates that one entity differs in some specified way from a reference entity defined under an RSA (Reference Software/Standard/Specification Agreement or similar) baseline.
-
C.
differenceFromStates
Indicates that one state or condition is distinct from, or deviates in some way from, another state or condition.
-
D.
differenceDescription
Indicates a textual explanation that characterizes how two entities differ from each other.
-
E.
governanceDiffersFrom
Indicates that the form, structure, or style of governance of one entity is different from that of another entity.
- F. None of above. chosen
Provenance (4 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_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 8:18 p.m.