Triple
T8918351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reiser4 |
E212348
|
entity |
| Predicate | kernelMainlineStatus |
P86395
|
FINISHED |
| Object | not merged into mainline Linux kernel |
—
|
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: not merged into mainline Linux kernel | Statement: [Reiser4, kernelMainlineStatus, not merged into mainline Linux kernel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kernelMainlineStatus Context triple: [Reiser4, kernelMainlineStatus, not merged into mainline Linux kernel]
-
A.
kernelVersionLine
Indicates that a given line of text specifies or contains information about a kernel version.
-
B.
kernelVersion
Indicates the specific operating system kernel version associated with an entity.
-
C.
KernelFoundedIn
Indicates that a kernel (such as an operating system kernel or similar core software component) was established, created, or first introduced in a specific time or place.
-
D.
kernelInterfaceIntroduced
Indicates that a new interface has been added or exposed within the kernel.
-
E.
kernelFamily
Indicates that one kernel is a member of, or derived from, a particular family or class of related kernels.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66120eb08190913ab6c42f26ffb8 |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc600a59708190ae426044bbcd7929 |
completed | April 1, 2026, midnight |
Created at: March 30, 2026, 6:56 p.m.