Triple
T1831424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fedora Kinoite |
E40768
|
entity |
| Predicate | releaseCycle |
P16199
|
FINISHED |
| Object | time-based Fedora release schedule |
—
|
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: time-based Fedora release schedule | Statement: [Fedora Kinoite, releaseCycle, time-based Fedora release schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseCycle Context triple: [Fedora Kinoite, releaseCycle, time-based Fedora release schedule]
-
A.
releaseSchedule
Indicates the planned timing and sequence for when something (such as a product, update, or content) will be made available or launched.
-
B.
releaseVersion
Indicates the specific version identifier associated with a particular release of something (e.g., software, product, or document).
-
C.
standardReleaseCadence
chosen
Indicates a relationship where an entity follows a regular, predefined schedule or frequency for releasing updates or versions.
-
D.
releaseStatus
Indicates the current state or phase of an item’s release process (e.g., planned, in progress, or completed).
-
E.
releaseChannel
Indicates the distribution pathway or medium through which something (such as a product, update, or content) is made available or delivered to its recipients.
- 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_69a8864644bc8190b2358ab897194ac1 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb45402688190b9a535b14030c354 |
completed | March 7, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69abafd6a9948190ac2b2743db6f8f69 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:32 p.m.