Triple
T28505844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ubuntu Kylin |
E721361
|
entity |
| Predicate | hasLongTermSupportReleases |
P25605
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ubuntu Kylin, hasLongTermSupportReleases, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLongTermSupportReleases Context triple: [Ubuntu Kylin, hasLongTermSupportReleases, yes]
-
A.
hasLTSReleases
chosen
Indicates that an entity provides or is associated with one or more Long-Term Support (LTS) releases.
-
B.
isLTS
Indicates that one system or specification is a labeled transition system (LTS) representation of another, capturing its states and labeled transitions.
-
C.
supportsReleasesOf
Indicates that one entity provides assistance, resources, or endorsement for the publication or rollout of another entity’s releases.
-
D.
endOfLongTermSupportDate
Indicates the calendar date on which long-term support for a product, service, or version officially ends.
-
E.
stableReleasesMaintainedBy
Indicates that the stable (non-development) releases of a software project are currently being maintained or supported by a particular 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 28, 2026, 3:09 a.m.