Triple
T2693954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 100BASE‑TX |
E58466
|
entity |
| Predicate | bitRatePerDirection |
P1376
|
FINISHED |
| Object | 100 Mbit/s in full-duplex |
—
|
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: 100 Mbit/s in full-duplex | Statement: [100BASE‑TX, bitRatePerDirection, 100 Mbit/s in full-duplex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bitRatePerDirection Context triple: [100BASE‑TX, bitRatePerDirection, 100 Mbit/s in full-duplex]
-
A.
dataRate
chosen
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
B.
packetDirection
Indicates the direction in which a data packet is traveling between network endpoints (e.g., inbound or outbound).
-
C.
dataRateGeneration
Indicates the rate at which data is produced or generated over time in a given context.
-
D.
maxSpatialStreams
Indicates the maximum number of simultaneous spatial data streams that can be used or supported in a communication or processing context.
-
E.
maxDataTransferMode
Indicates the data transfer mode in which the maximum possible data throughput is achieved between entities.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda0f43b08190a5abd936b14603b7 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81ea5d88190ab5c8f8b8064b931 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.