Triple
T4476398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gigabit Ethernet |
E100018
|
entity |
| Predicate | cableTypeFor1000BASE-T |
P1373
|
FINISHED |
| Object | Category 5e or better twisted pair |
—
|
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: Category 5e or better twisted pair | Statement: [Gigabit Ethernet, cableTypeFor1000BASE-T, Category 5e or better twisted pair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cableTypeFor1000BASE-T Context triple: [Gigabit Ethernet, cableTypeFor1000BASE-T, Category 5e or better twisted pair]
-
A.
cableType
chosen
Indicates the specific kind or category of cable associated with or used by an entity.
-
B.
tunnelType
Indicates the specific kind or classification of a tunnel associated with an entity.
-
C.
energyEfficientEthernetStandard
Indicates that the subject conforms to or supports the Energy-Efficient Ethernet (EEE) standard for reducing power consumption in Ethernet networking.
-
D.
cableImpedance
Indicates the electrical opposition (impedance) presented by a cable to alternating current flow in a circuit.
-
E.
transmissionTypeSupported
Indicates that a particular type of transmission is compatible with or can be used by a given system, device, or component.
- 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.