Triple
T27866470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 20000-12 |
E704371
|
entity |
| Predicate | relatesToFramework |
P200603
|
FINISHED |
| Object | CMMI for Services |
—
|
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: CMMI for Services | Statement: [ISO/IEC 20000-12, relatesToFramework, CMMI for Services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatesToFramework Context triple: [ISO/IEC 20000-12, relatesToFramework, CMMI for Services]
-
A.
isPartOfFramework
Indicates that one entity functions as a component, module, or element within a larger structured framework or system.
-
B.
appliesFramework
Indicates that one entity uses or implements a particular framework in relation to another entity or context.
-
C.
parentFramework
Indicates that one framework serves as the higher-level or containing framework from which another framework is derived, organized, or structured.
-
D.
frameworkFor
Indicates that one entity serves as a supporting structure, system, or basis that organizes, guides, or enables the development or functioning of another entity.
-
E.
belongsToFrameworkFamily
Indicates that one framework is a member of, or categorized under, a broader framework family or grouping.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
| PDg | Predicate description generation | batch_69ff9b19f254819099bb9c034d2b399b |
completed | May 9, 2026, 8:37 p.m. |
Created at: April 27, 2026, 6:21 p.m.