Triple
T18230064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time-Triggered Protocol |
E436521
|
entity |
| Predicate | schedulingBasis |
P89710
|
FINISHED |
| Object | global time |
—
|
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: global time | Statement: [Time-Triggered Protocol, schedulingBasis, global time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schedulingBasis Context triple: [Time-Triggered Protocol, schedulingBasis, global time]
-
A.
schedulingUnit
Indicates a relationship where one entity functions as a unit or block used for organizing, allocating, or managing time or resources in a schedule.
-
B.
schedulingRule
Indicates a rule or constraint that governs when, how, or under what conditions an event or task may be scheduled.
-
C.
planningBasis
chosen
Indicates that one entity serves as the foundational reference or justification used by another entity when making plans or preparing actions.
-
D.
schedulePattern
Indicates a recurring or structured timing relationship that defines when an event or action is scheduled to occur.
-
E.
schedulingStrategy
Indicates how tasks, events, or operations are ordered and allocated over time or resources relative to one another.
- 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.