Triple
T14421820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android 5.0 Lollipop |
E357601
|
entity |
| Predicate | kernelVersionRange |
P11239
|
FINISHED |
| Object | Linux kernel 3.4 to 3.10 (typical) |
—
|
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: Linux kernel 3.4 to 3.10 (typical) | Statement: [Android 5.0 Lollipop, kernelVersionRange, Linux kernel 3.4 to 3.10 (typical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kernelVersionRange Context triple: [Android 5.0 Lollipop, kernelVersionRange, Linux kernel 3.4 to 3.10 (typical)]
-
A.
kernelVersion
Indicates the specific operating system kernel version associated with an entity.
-
B.
kernelVersionLine
Indicates that a given line of text specifies or contains information about a kernel version.
-
C.
usedInVersionRange
chosen
Indicates that something is applicable, valid, or in effect only within a specified range of versions.
-
D.
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.
-
E.
kernelMainlineStatus
Indicates whether something is part of, aligned with, or supported by the mainline (upstream) version of a kernel.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91102c3c81908f571a1fff3bdd47 |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.