Triple
T9945660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linux kernel release process |
E195196
|
entity |
| Predicate | typicalReleaseFrequency |
P56156
|
FINISHED |
| Object | roughly every 9 to 10 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: roughly every 9 to 10 weeks | Statement: [Linux kernel release process, typicalReleaseFrequency, roughly every 9 to 10 weeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalReleaseFrequency Context triple: [Linux kernel release process, typicalReleaseFrequency, roughly every 9 to 10 weeks]
-
A.
standardReleaseCadence
Indicates a relationship where an entity follows a regular, predefined schedule or frequency for releasing updates or versions.
-
B.
typicalUpdateFrequency
chosen
Indicates how often an entity is usually updated or refreshed over time.
-
C.
typicalReleaseWindow
Indicates the usual or expected time period during which something is released or made available.
-
D.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
E.
laterFrequency
Indicates that one event, state, or action occurs with a lower frequency than another in a temporal sequence.
- 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_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. |
Created at: March 30, 2026, 8:45 p.m.