Triple
T4616846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 27018 |
E100887
|
entity |
| Predicate | canBeCertifiedAgainst |
P23438
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ISO/IEC 27018, canBeCertifiedAgainst, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeCertifiedAgainst Context triple: [ISO/IEC 27018, canBeCertifiedAgainst, yes]
-
A.
certificationBy
Indicates that one entity formally attests to, approves, or validates the qualifications, standards, or authenticity of another entity.
-
B.
certificationScope
chosen
Indicates the specific range, domain, or subject matter that a given certification covers or applies to.
-
C.
isTCKCertified
Indicates that an entity has successfully passed the Technology Compatibility Kit (TCK) tests and is officially certified as compliant with the relevant specification.
-
D.
requiresCertification
Indicates that one entity can only be performed, accessed, or considered valid if another entity has an appropriate certification.
-
E.
mayAlsoBeAccreditedTo
Indicates that the credit or attribution for something can additionally be assigned to another entity beyond the primary one.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e098c08190b769e76937dff700 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.