Triple
T14936249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android 8.0 Oreo |
E372400
|
entity |
| Predicate | supportsKernelType |
P82499
|
FINISHED |
| Object | monolithic 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: monolithic Linux kernel | Statement: [Android 8.0 Oreo, supportsKernelType, monolithic Linux kernel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsKernelType Context triple: [Android 8.0 Oreo, supportsKernelType, monolithic Linux kernel]
-
A.
hasKernelType
chosen
Indicates that an entity possesses or is associated with a specific type or classification of kernel.
-
B.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
C.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
D.
hasKernel
Indicates that one entity functions as the kernel (core or central component) of another entity.
-
E.
supportsModelType
Indicates that an entity is compatible with, or can operate using, a specified model type.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded647ae388190a0e97c03f2a4d832 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:37 a.m.