Triple
T28400349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OC-3 |
E719379
|
entity |
| Predicate | approximateDataRate |
P111712
|
FINISHED |
| Object | 155 Mbps |
—
|
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: 155 Mbps | Statement: [OC-3, approximateDataRate, 155 Mbps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDataRate Context triple: [OC-3, approximateDataRate, 155 Mbps]
-
A.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
B.
hasApproximateRate
chosen
Indicates that one entity is associated with another entity representing an estimated or non-exact rate or frequency.
-
C.
approximateOperatingSpeed
Indicates that one entity specifies or characterizes the estimated or typical operating speed of another entity, rather than an exact value.
-
D.
dataRateGeneration
Indicates the rate at which data is produced or generated over time in a given context.
-
E.
dataRateLowSpeed
Indicates that the data transmission rate is at a relatively low speed or bandwidth level.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 28, 2026, 1:19 a.m.