Triple
T8284346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RT-Thread |
E193753
|
entity |
| Predicate | hasScheduler |
P82500
|
FINISHED |
| Object | priority-based scheduler |
—
|
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: priority-based scheduler | Statement: [RT-Thread, hasScheduler, priority-based scheduler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScheduler Context triple: [RT-Thread, hasScheduler, priority-based scheduler]
-
A.
supportsSchedulerTracing
Indicates that an entity enables or is compatible with tracing or monitoring of scheduler-related activities or events.
-
B.
hasScheduleType
Indicates that an entity is associated with a particular kind or category of schedule (e.g., recurring, one-time, or specific scheduling pattern).
-
C.
hasTimer
Indicates that an entity is associated with or controlled by a timer mechanism that measures or limits a duration or interval.
-
D.
hasExecutor
Indicates that a particular action, task, or legal instrument is carried out or implemented by a specified responsible agent or party.
-
E.
usedForScheduling
Indicates that something is employed to plan, arrange, or coordinate the timing of events, tasks, or activities.
- 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.