Triple
T8284311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RT-Thread |
E193753
|
entity |
| Predicate | hasKernelType |
P82499
|
FINISHED |
| Object | preemptive multitasking |
—
|
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: preemptive multitasking | Statement: [RT-Thread, hasKernelType, preemptive multitasking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKernelType Context triple: [RT-Thread, hasKernelType, preemptive multitasking]
-
A.
hasKeyType
Indicates that an entity possesses or is associated with a specific category or type of key.
-
B.
hasTypeSystem
Indicates that an entity employs, is governed by, or is associated with a particular type system (a defined set of rules for classifying and constraining types).
-
C.
hasPackageType
Indicates that an entity is associated with or classified under a particular type or category of package.
-
D.
hasModelType
Indicates that an entity is associated with or classified under a specific model type.
-
E.
hasKnotType
Indicates that one entity is characterized by, or associated with, a specific type or classification of knot.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad0535081908bb234cfc0e32b32 |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:52 p.m.