Triple
T1016019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 15288 |
E21930
|
entity |
| Predicate | conformsToModel |
P3994
|
FINISHED |
| Object | process-based life cycle model |
—
|
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: process-based life cycle model | Statement: [ISO/IEC 15288, conformsToModel, process-based life cycle model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conformsToModel Context triple: [ISO/IEC 15288, conformsToModel, process-based life cycle model]
-
A.
conformsTo
chosen
Indicates that one entity complies with, follows, or is in accordance with a specified standard, specification, rule, or guideline.
-
B.
hasConformanceRequirements
Indicates that an entity is subject to specific rules, standards, or criteria that it must satisfy or comply with.
-
C.
hasModelType
Indicates that an entity is associated with or classified under a specific model type.
-
D.
hasModelledFor
Indicates that one entity has served as a model for another entity, typically in a professional or representational context such as art, photography, or fashion.
-
E.
supportsModelType
Indicates that an entity is compatible with, or can operate using, a specified model type.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c1e9d08190baf7e81f3777168d |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.