Triple
T31792983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SRP |
E811518
|
entity |
| Predicate | violationExample |
P2111
|
FINISHED |
| Object | class handling business logic and persistence together |
—
|
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: class handling business logic and persistence together | Statement: [SRP, violationExample, class handling business logic and persistence together]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: violationExample Context triple: [SRP, violationExample, class handling business logic and persistence together]
-
A.
violationOf
Indicates that one entity breaches, disobeys, or infringes upon a rule, law, agreement, or right associated with another entity.
-
B.
wouldViolate
Indicates that performing the specified action or condition would break, infringe, or be inconsistent with a given rule, constraint, or obligation.
-
C.
violationContext
Indicates the specific circumstances, conditions, or situational factors under which a violation occurs or is considered to have occurred.
-
D.
violatedPrinciple
chosen
Indicates that an entity has broken, disregarded, or acted contrary to a specified rule, norm, or guiding principle.
-
E.
violationExperienced
Indicates that an entity has been subjected to or has undergone a violation, such as a breach of rights, rules, or agreed standards.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:39 p.m.