Triple
T9945659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linux kernel release process |
E195196
|
entity |
| Predicate | typicalReleaseCandidateCycleLength |
P91287
|
FINISHED |
| Object | approximately 6 to 8 weeks |
—
|
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: approximately 6 to 8 weeks | Statement: [Linux kernel release process, typicalReleaseCandidateCycleLength, approximately 6 to 8 weeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalReleaseCandidateCycleLength Context triple: [Linux kernel release process, typicalReleaseCandidateCycleLength, approximately 6 to 8 weeks]
-
A.
standardReleaseCadence
Indicates a relationship where an entity follows a regular, predefined schedule or frequency for releasing updates or versions.
-
B.
typicalReleaseWindow
Indicates the usual or expected time period during which something is released or made available.
-
C.
targetRelease
Indicates the specific release or version that an item (such as a feature, fix, or component) is planned or designated to be delivered in.
-
D.
evaluationCycle
Indicates the recurring period or sequence in which evaluations or assessments are conducted and reviewed.
-
E.
betaReleaseDate
Indicates the date on which a product or system is first released in its beta version for testing or limited use.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb61561848190aba7250f3b3c4ed5 |
completed | April 2, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:45 p.m.