Triple
T18230083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time-Triggered Protocol |
E436521
|
entity |
| Predicate | messageTrigger |
P80191
|
FINISHED |
| Object | predefined time slots |
—
|
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: predefined time slots | Statement: [Time-Triggered Protocol, messageTrigger, predefined time slots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: messageTrigger Context triple: [Time-Triggered Protocol, messageTrigger, predefined time slots]
-
A.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
B.
typicalTrigger
Indicates that one entity commonly or characteristically causes, initiates, or brings about the occurrence of another entity or event.
-
C.
sentSignalTo
Indicates that one entity transmitted a signal or message to another entity.
-
D.
notificationType
chosen
Indicates the specific category or kind of notification associated with an event or action.
-
E.
sentSignalFrom
Indicates that one entity transmitted or emitted a signal originating from a specified source entity.
- 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_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. |
Created at: April 10, 2026, 10:33 a.m.