Triple
T4384823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time-Triggered Ethernet |
E99216
|
entity |
| Predicate | usesSchedulingMethod |
P52664
|
FINISHED |
| Object | time-division multiple access |
—
|
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: time-division multiple access | Statement: [Time-Triggered Ethernet, usesSchedulingMethod, time-division multiple access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSchedulingMethod Context triple: [Time-Triggered Ethernet, usesSchedulingMethod, time-division multiple access]
-
A.
usedForScheduling
chosen
Indicates that something is employed to plan, arrange, or coordinate the timing of events, tasks, or activities.
-
B.
usesScheduleFormat
Indicates that one entity adopts or follows the schedule structure, pattern, or formatting defined by another entity.
-
C.
usedInSchedulingSystems
Indicates that something is employed as a component or mechanism within scheduling systems to plan, allocate, or manage tasks, resources, or time.
-
D.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
-
E.
schedulingRule
Indicates a rule or constraint that governs when, how, or under what conditions an event or task may be scheduled.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35264e44c81908dd0e0a81f1353bb |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.