Triple
T20844533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 50 Gigabit Ethernet |
E513185
|
entity |
| Predicate | usesLaneConfiguration |
P39910
|
FINISHED |
| Object | single-lane 50G |
—
|
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: single-lane 50G | Statement: [50 Gigabit Ethernet, usesLaneConfiguration, single-lane 50G]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLaneConfiguration Context triple: [50 Gigabit Ethernet, usesLaneConfiguration, single-lane 50G]
-
A.
canUseLaneConfiguration
Indicates that an entity is permitted or able to operate under a specified lane configuration.
-
B.
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).
-
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.
usesPhysicalLanes
Indicates that an entity operates or organizes movement through distinct, physically separated lanes or pathways.
-
E.
laneConfigurationChange
Indicates a change in the number, type, or arrangement of lanes along a roadway segment.
- 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_69e0b4f4898081908209e58edb8f9c45 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c34deef88190992b959b83bc59b1 |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:43 p.m.