Triple
T18230057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time-Triggered Protocol |
E436521
|
entity |
| Predicate | supportsHardRealTime |
P130335
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Time-Triggered Protocol, supportsHardRealTime, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHardRealTime Context triple: [Time-Triggered Protocol, supportsHardRealTime, true]
-
A.
supportsRealTimeMonitoring
Indicates that an entity provides the capability to observe and track relevant data or events continuously as they occur in real time.
-
B.
hasRealTimeInformation
Indicates that up-to-date, continuously refreshed information is available about the related entity or event.
-
C.
supportsFrameRates
Indicates that one entity is capable of operating with, handling, or being compatible with the specified frame rates of another entity.
-
D.
supportsTimescale
Indicates that one entity is capable of operating with, accommodating, or being compatible with a specified timescale or range of temporal resolutions.
-
E.
supportsMultiprogramming
Indicates that a system, component, or environment is capable of executing or managing multiple programs or processes concurrently.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f4b284a8819088456c2af5fa1de5 |
completed | April 19, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:33 a.m.