Triple
T30152077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Criteria |
E766421
|
entity |
| Predicate | evaluationMethodologyDefinedIn |
P17142
|
FINISHED |
| Object | ISO/IEC 18045 |
—
|
NE NERFINISHED |
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: ISO/IEC 18045 | Statement: [Common Criteria, evaluationMethodologyDefinedIn, ISO/IEC 18045]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaluationMethodologyDefinedIn Context triple: [Common Criteria, evaluationMethodologyDefinedIn, ISO/IEC 18045]
-
A.
evaluationModel
Indicates a relationship where one entity serves as a model, standard, or framework used to assess, judge, or measure the performance or quality of another entity.
-
B.
evaluationBasis
chosen
Indicates the criteria, standards, or reference framework used to judge, assess, or measure something in an evaluation process.
-
C.
evaluationUse
Indicates that something is used as a basis, tool, or resource for evaluating or assessing something else.
-
D.
assessmentMethod
Indicates the method or procedure used to evaluate, measure, or judge something.
-
E.
evaluationAspect
Indicates the specific dimension or criterion of performance or quality that is being assessed within an evaluation.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed4df5081908d1431e3a1a1fb0e |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:20 p.m.