Triple
T31752392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ORPC 1.1 Competence |
E810459
|
entity |
| Predicate | violationMayLeadTo |
P36372
|
FINISHED |
| Object | professional discipline |
—
|
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: professional discipline | Statement: [ORPC 1.1 Competence, violationMayLeadTo, professional discipline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: violationMayLeadTo Context triple: [ORPC 1.1 Competence, violationMayLeadTo, professional discipline]
-
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.
violationConsequences
chosen
Indicates the negative outcomes, penalties, or repercussions that result from a violation of a rule, law, or agreement.
-
D.
allegedViolationSystem
Indicates a system is reported or suspected to have violated a rule, policy, or regulation, without the violation being legally or formally established.
-
E.
violationContext
Indicates the specific circumstances, conditions, or situational factors under which a violation occurs or is considered to have occurred.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab5390208190a05fda888425b9d4 |
completed | May 3, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:28 p.m.