Triple
T16921848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpaceWire |
E410460
|
entity |
| Predicate | dataRateRange |
P110272
|
FINISHED |
| Object | 2 Mbit/s to 400 Mbit/s |
—
|
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: 2 Mbit/s to 400 Mbit/s | Statement: [SpaceWire, dataRateRange, 2 Mbit/s to 400 Mbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataRateRange Context triple: [SpaceWire, dataRateRange, 2 Mbit/s to 400 Mbit/s]
-
A.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
B.
dataRateGeneration
Indicates the rate at which data is produced or generated over time in a given context.
-
C.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
D.
referenceRate
Indicates that one entity serves as the benchmark or base rate used to determine or adjust the rate applied to another entity or transaction.
-
E.
bitrateRange
chosen
Indicates the range of data transfer rates (minimum to maximum bitrate) within which something, such as a media stream or encoding, operates.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cdef7df881908b69aa3c4f50ef94 |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.