Triple
T28582523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PCI Secure Software Lifecycle Standard |
E723414
|
entity |
| Predicate | lifecycleCoverage |
P142850
|
FINISHED |
| Object | design phase |
—
|
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: design phase | Statement: [PCI Secure Software Lifecycle Standard, lifecycleCoverage, design phase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifecycleCoverage Context triple: [PCI Secure Software Lifecycle Standard, lifecycleCoverage, design phase]
-
A.
lifeCycleCoverage
chosen
Indicates that one entity addresses, spans, or is applicable across specific stages or the entirety of another entity’s lifecycle.
-
B.
lifetimeCovers
Indicates that a specified coverage, policy, or protection applies for the entire duration of an entity’s existence or validity, without temporal gaps or renewals.
-
C.
lifetimeCovers
Indicates that a coverage, warranty, or protection remains valid for the entire lifetime of the specified subject or item.
-
D.
lifecycleType
Indicates the specific stage or pattern within an entity’s overall lifecycle that characterizes how it begins, evolves, and ends.
-
E.
lifecycleModel
Indicates that one entity defines or follows the structured sequence of phases or stages governing the development, use, and retirement of another entity.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 4:15 a.m.