Triple
T15921468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CEP |
E386102
|
entity |
| Predicate | attestsComplianceWith |
P42399
|
FINISHED |
| Object | European Pharmacopoeia standards |
—
|
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: European Pharmacopoeia standards | Statement: [CEP, attestsComplianceWith, European Pharmacopoeia standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attestsComplianceWith Context triple: [CEP, attestsComplianceWith, European Pharmacopoeia standards]
-
A.
indicatesComplianceWith
chosen
Indicates that one entity conforms to, satisfies, or adheres to the rules, standards, or requirements specified by another entity or framework.
-
B.
providesCompliance
Indicates that one entity supplies or ensures adherence to required rules, standards, or regulations for another entity.
-
C.
evaluatesComplianceWith
Indicates that one entity assesses whether another entity or its behavior meets specified rules, standards, or requirements.
-
D.
regulatesComplianceWith
Indicates that one entity oversees, enforces, or sets rules to ensure another entity adheres to specified standards, laws, or requirements.
-
E.
hasComplianceStatement
Indicates that an entity is associated with a formal declaration that it adheres to specified rules, standards, or regulatory requirements.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.