Triple
T4476416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gigabit Ethernet |
E100018
|
entity |
| Predicate | supportsAutoMDI_X |
P18341
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Gigabit Ethernet, supportsAutoMDI_X, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAutoMDI_X Context triple: [Gigabit Ethernet, supportsAutoMDI_X, true]
-
A.
supportsMDI_MDIX
chosen
Indicates that a device or interface is capable of operating in both MDI and MDIX modes, automatically handling crossover of transmit and receive signal pairs.
-
B.
usesAutoNegotiation
Indicates that one entity configures or operates a connection using automatic negotiation of parameters (such as speed or duplex) with another entity.
-
C.
supportsSingleFrequencyNetworks
Indicates that an entity enables or is compatible with operating in single frequency networks, where multiple transmitters use the same frequency to provide coordinated coverage.
-
D.
supportsVLANTagging
Indicates that one entity provides the capability for another entity or interface to handle and process VLAN-tagged network traffic.
-
E.
usesMDI
Indicates that one entity employs or operates another entity through a Multi-Document Interface (MDI) framework or mechanism.
- 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_69b34553cbe48190afa8ac1cac285b86 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35728ed508190ba0e882fa62d8848 |
completed | March 13, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69b3563d63008190816e37027e761375 |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:35 p.m.