Triple
T29482694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CentOS Atomic Host |
E747832
|
entity |
| Predicate | hasLifecycleStatus |
P31531
|
FINISHED |
| Object | discontinued |
—
|
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: discontinued | Statement: [CentOS Atomic Host, hasLifecycleStatus, discontinued]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLifecycleStatus Context triple: [CentOS Atomic Host, hasLifecycleStatus, discontinued]
-
A.
lifecycleStatus
chosen
Indicates the current phase or condition of an entity within its overall lifecycle or progression from creation to termination.
-
B.
hasLifetimeStatus
Indicates that an entity is associated with a status or condition that applies for the entire duration of its existence.
-
C.
hasLiveOnlyStatus
Indicates that the entity is currently in a live state and does not possess any other status.
-
D.
hasExistenceStatus
Indicates that an entity is associated with a particular state of existence, such as being current, historical, planned, or no longer existing.
-
E.
lifecycleType
Indicates the specific stage or pattern within an entity’s overall lifecycle that characterizes how it begins, evolves, and ends.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 28, 2026, 4:05 p.m.