Triple
T28610182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smack |
E724149
|
entity |
| Predicate | mainlineStatus |
P86395
|
FINISHED |
| Object | 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: merged into mainline Linux kernel | Statement: [Smack, mainlineStatus, merged into mainline Linux kernel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainlineStatus Context triple: [Smack, mainlineStatus, merged into mainline Linux kernel]
-
A.
mainLine
Indicates that something serves as the primary or central line, route, or sequence among a set of related lines.
-
B.
kernelMainlineStatus
chosen
Indicates whether something is part of, aligned with, or supported by the mainline (upstream) version of a kernel.
-
C.
modernStatus
Indicates the current or contemporary condition, classification, or standing of an entity in the present time.
-
D.
lineStatus
Indicates the current operational or functional state of a line or connection within a system.
-
E.
mainWorkStatus
Indicates the current primary state or condition of a work (such as active, completed, pending, or inactive) within a given process or system.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 4:29 a.m.