Triple
T28400350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OC-3 |
E719379
|
entity |
| Predicate | payloadRate |
P1376
|
FINISHED |
| Object | 148.608 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: 148.608 Mbit/s | Statement: [OC-3, payloadRate, 148.608 Mbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadRate Context triple: [OC-3, payloadRate, 148.608 Mbit/s]
-
A.
payloadCount
Indicates the number of payload items associated with or carried by a given entity or operation.
-
B.
exportRate
Indicates the rate or proportion at which goods, services, or resources are sent out from one entity or region to others.
-
C.
dataRate
chosen
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
D.
payloadServiced
Indicates that a payload has been attended to, maintained, or otherwise handled to fulfill its required service or operational needs.
-
E.
ratedPayload
Indicates the maximum payload or load that an object, system, or component is officially rated or certified to carry, handle, or support.
- 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_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:19 a.m.