Triple
T20904830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 100 Gigabit Ethernet |
E514764
|
entity |
| Predicate | usesLaneArchitecture |
P39910
|
FINISHED |
| Object | 4 lanes of 25 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: 4 lanes of 25 Gbit/s | Statement: [100 Gigabit Ethernet, usesLaneArchitecture, 4 lanes of 25 Gbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLaneArchitecture Context triple: [100 Gigabit Ethernet, usesLaneArchitecture, 4 lanes of 25 Gbit/s]
-
A.
usesPhysicalLanes
Indicates that an entity operates or organizes movement through distinct, physically separated lanes or pathways.
-
B.
hasDedicatedLanes
Indicates that specific lanes within a route or roadway are reserved exclusively for a particular type of traffic or use.
-
C.
hasLanes
Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
-
D.
hasSecurityLanes
Indicates that an entity is equipped with designated security screening lanes for processing people or items.
-
E.
hasLaneConfigurations
chosen
Indicates that an entity is associated with one or more specific arrangements or patterns of lanes (e.g., number, type, or direction of lanes).
- 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e8ff36488190987ecdfcbed4220c |
completed | April 21, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:47 p.m.