Triple
T5678915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CENELEC |
E125152
|
entity |
| Predicate | typeOfStandards |
P43031
|
FINISHED |
| Object | voluntary 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: voluntary standards | Statement: [CENELEC, typeOfStandards, voluntary standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfStandards Context triple: [CENELEC, typeOfStandards, voluntary standards]
-
A.
standardsType
chosen
Indicates the classification or category of standards that apply to or are associated with an entity or activity.
-
B.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
C.
legalStandardType
Indicates the specific type or category of legal standard that governs or applies to a given legal rule, decision, or evaluation.
-
D.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
E.
industryStandardFor
Indicates that something is widely accepted or recognized as the conventional or benchmark practice, specification, or norm within a particular industry.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.