Triple
T908620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10GBASE-ER |
E19605
|
entity |
| Predicate | opticalInterfaceType |
P7239
|
FINISHED |
| Object | serial 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: serial 10 Gbit/s | Statement: [10GBASE-ER, opticalInterfaceType, serial 10 Gbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opticalInterfaceType Context triple: [10GBASE-ER, opticalInterfaceType, serial 10 Gbit/s]
-
A.
usesOpticsType
chosen
Indicates that one entity employs or is characterized by a specific type of optical system or technology.
-
B.
cableType
Indicates the specific kind or category of cable associated with or used by an entity.
-
C.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
D.
requiresModeConditioningPatchCordOnMultimode
Indicates that a mode-conditioning patch cord must be used when connecting to or operating over multimode fiber.
-
E.
usesAutoNegotiation
Indicates that one entity configures or operates a connection using automatic negotiation of parameters (such as speed or duplex) with another entity.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3bcad2481908b83575b2fb80d14 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b28ff5948190982c4439eadf9d87 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:39 p.m.