Triple
T9899670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOC 1 |
E182251
|
entity |
| Predicate | controlCategoriesMayInclude |
P70092
|
FINISHED |
| Object | data processing |
—
|
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: data processing | Statement: [SOC 1, controlCategoriesMayInclude, data processing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlCategoriesMayInclude Context triple: [SOC 1, controlCategoriesMayInclude, data processing]
-
A.
coreCategory
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
-
B.
protectedCategory
Indicates that one entity is classified under a legally or formally recognized group that is granted special protection from discrimination or adverse treatment.
-
C.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
-
D.
protectionCategory
Indicates a classification relationship where an entity is assigned to a specific type or level of protection based on defined protective criteria or rules.
-
E.
containsCategory
chosen
Indicates that one entity includes or encompasses a specific category as part of its classification or organizational structure.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4adc03481909e0f657db01e5bab |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:40 p.m.