Triple
T7937811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Linux |
E184325
|
entity |
| Predicate | supportLifecycle |
P79898
|
FINISHED |
| Object | RHEL-aligned lifecycle |
—
|
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: RHEL-aligned lifecycle | Statement: [Rocky Linux, supportLifecycle, RHEL-aligned lifecycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportLifecycle Context triple: [Rocky Linux, supportLifecycle, RHEL-aligned lifecycle]
-
A.
supportBase
Indicates that one entity serves as a foundational or backing structure that physically or functionally supports another entity.
-
B.
supportsLifespan
Indicates that one entity contributes to maintaining, extending, or enabling the full duration of another entity’s life or functional existence.
-
C.
supportsLife
Indicates that one entity provides conditions or resources that allow another entity to live, grow, or remain biologically viable.
-
D.
supportStyle
Indicates the manner or approach by which one entity provides assistance or backing to another.
-
E.
lifecycleFeature
Indicates that one entity is a feature, phase, or characteristic associated with a particular stage in the lifecycle of another entity.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aef2394819086eea1f6ab117aed |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:08 p.m.