Triple
T34673441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimberley Process Certification Scheme |
E890437
|
entity |
| Predicate | certificateMustBe |
P179604
|
FINISHED |
| Object | tamper-resistant |
—
|
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: tamper-resistant | Statement: [Kimberley Process Certification Scheme, certificateMustBe, tamper-resistant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: certificateMustBe Context triple: [Kimberley Process Certification Scheme, certificateMustBe, tamper-resistant]
-
A.
certificateGrantedBy
Indicates that a certificate was issued or formally granted by a specific authority or organization to another entity.
-
B.
certificateAvailable
Indicates that a valid certificate is present and accessible for use in the given context.
-
C.
certificateType
Indicates the specific kind or category of certificate associated with an entity or relationship.
-
D.
certificateStandard
Indicates that something conforms to, or is governed by, a particular certification standard or specification.
-
E.
certificateIssued
Indicates that an official certificate has been formally created and granted by an issuing authority to a recipient or for a specific subject.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72322256c8190afb14d73a2612b6f |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: May 1, 2026, 2:05 a.m.