Triple
T19234722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GMII |
E480963
|
entity |
| Predicate | supportsEthernetType |
P109386
|
FINISHED |
| Object | Gigabit Ethernet |
—
|
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: Gigabit Ethernet | Statement: [GMII, supportsEthernetType, Gigabit Ethernet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsEthernetType Context triple: [GMII, supportsEthernetType, Gigabit Ethernet]
-
A.
energyEfficientEthernetStandard
Indicates that the subject conforms to or supports the Energy-Efficient Ethernet (EEE) standard for reducing power consumption in Ethernet networking.
-
B.
supportedNetwork
chosen
Indicates that one entity (such as a device, service, or application) is compatible with, operates on, or is designed to work over a specified network or type of network.
-
C.
supportsLinkAggregation
Indicates that one entity provides or is compatible with link aggregation capabilities for combining multiple network connections into a single logical link.
-
D.
supportsVLANTagging
Indicates that one entity provides the capability for another entity or interface to handle and process VLAN-tagged network traffic.
-
E.
supportsWiFiStandard
Indicates that one entity is compatible with and able to operate using a specified Wi-Fi communication standard defined by 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faeb53988190b83afee9974058c6 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:26 p.m.