Triple
T892346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10GBASE-LR |
E19267
|
entity |
| Predicate | nominalDataRate |
P1376
|
FINISHED |
| Object | 10 Gbit/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: 10 Gbit/s | Statement: [10GBASE-LR, nominalDataRate, 10 Gbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nominalDataRate Context triple: [10GBASE-LR, nominalDataRate, 10 Gbit/s]
-
A.
dataRate
chosen
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.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
D.
hasPostNominal
Indicates that an entity is associated with a post-nominal title, abbreviation, or letters that follow a name to denote qualifications, honors, or status.
-
E.
duplexMode
Indicates whether a communication link or device operates in half-duplex or full-duplex mode, defining if data can flow in one or both directions simultaneously.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad0304b081908d4c92bb2beadb81 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9372e88190b5a9db4afdc045c6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.