Triple
T8247098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ubuntu |
E192875
|
entity |
| Predicate | LTSReleaseCycle |
P16199
|
FINISHED |
| Object | two-year LTS release cycle |
—
|
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: two-year LTS release cycle | Statement: [Ubuntu, LTSReleaseCycle, two-year LTS release cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LTSReleaseCycle Context triple: [Ubuntu, LTSReleaseCycle, two-year LTS release cycle]
-
A.
hasLTSReleases
Indicates that an entity provides or is associated with one or more Long-Term Support (LTS) releases.
-
B.
endOfLongTermSupportDate
Indicates the calendar date on which long-term support for a product, service, or version officially ends.
-
C.
standardReleaseCadence
chosen
Indicates a relationship where an entity follows a regular, predefined schedule or frequency for releasing updates or versions.
-
D.
latestMajorVersionFamily
Indicates that one entity is the most recent major version within a defined version family or series relative to another entity.
-
E.
continuousVersionName
Indicates that one entity is the name or label assigned to a continuous or ongoing version 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7875318c819095f971ba513c54fd |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.